Opened 13 years ago
Closed 2 weeks ago
#8028 closed bug (not reproducible)
KDL: page fault at 0x8 (NULL dereference) in heap_allocate_from_bin
Reported by: | humdinger | Owned by: | mmlr |
---|---|---|---|
Priority: | low | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #9641 | |
Platform: | All |
Description
This is hrev42858, gcc2hybrid
I can't really remember what exactly was going on when this crash occured, but I took a picture... It starts with:
PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8, ip 0x80054bbb
I hope it's no duplicate, couldn't find an existing ticket after just a short search.
Are these kinds of reports helpful at all?
Attachments (3)
Change History (20)
by , 13 years ago
comment:1 by , 13 years ago
Keywords: | port heap added |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 13 years ago
Attached another KDL photo that seems to show the same issue. This time it's:
PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8, ip 0x8005683f
ETA: Haiku revision is hrev43696.
comment:3 by , 13 years ago
Milestone: | R1 → R1/alpha4 |
---|---|
Priority: | normal → high |
comment:4 by , 13 years ago
And another one. Attached kdl-3.jpg. This time I left the computer after 3 hours uptime for 30 minutes while it was building a Haiku image (jam -qj2, 2gb ram). Came back to KDL.
follow-up: 6 comment:5 by , 13 years ago
That last one isn't related, it has a different stack trace not pointing to the port heap. It'd probably warrant it's own ticket.
comment:6 by , 13 years ago
follow-up: 8 comment:7 by , 13 years ago
I found that last, kdl-3, being reproducible. I'm trying to build a current Haiku image from Haiku hrev43696 with "AddOptionalHaikuImagePackages DemoPackage_Data ;" in the UserBuildProfile. The KDL appears always while extracting the demo package into the image. The 50mb package extracts to about 75mb. I made sure the image is large enough...
When extracting the demo package with Expander, there's no problem. The email seen in the KDL looks OK too...
comment:8 by , 13 years ago
Replying to humdinger:
I found that last, kdl-3, being reproducible.
My previous comment might have been a bit to concise. :-) The crash is in the FD path info code Clemens introduced a while ago. It has a few issues which I commented on on the commit list. Since Clemens didn't have the time to address them, he removed the code for the time being (in hrev43739). So no need to track that KDL.
comment:9 by , 12 years ago
Milestone: | R1/alpha4 → R1 |
---|
comment:10 by , 12 years ago
Blocking: | 9641 added |
---|
comment:11 by , 11 years ago
Cc: | added |
---|
comment:12 by , 6 years ago
Summary: | PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8, ip 0x80054bbb → KDL: page fault at 0x8 (NULL dereference) in heap_allocate_from_bin |
---|
comment:14 by , 6 years ago
Cc: | removed |
---|
comment:15 by , 5 years ago
Glancing at this again: It seems the heap in question is the "debug heap", not the "object cache heap" as we use normally. So this is probably low-priority at this point, if it's reproducible at all.
comment:16 by , 5 years ago
Priority: | high → low |
---|
comment:17 by , 2 weeks ago
Keywords: | port heap removed |
---|---|
Resolution: | → not reproducible |
Status: | assigned → closed |
KDL: vm_page_fault