#8115 closed bug (fixed)
vm_page_fault: unhandled page at 0xdeadbeef, ip 0x8006176d
Reported by: | humdinger | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | port heap | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev42901.
I recently had a KDL while only having idly open 2 Tracker windows, a query result window, a Mail window. Plus a Web+ with ca. 6 tabs, 4 of those loading pages.
First line:
PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbeef, ip 0x8006176d
The rest attached as KDL.jpg.
Attachments (1)
Change History (8)
by , 13 years ago
follow-up: 2 comment:1 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Looks like an uninitialized pointer in the ports code somewhere...
follow-up: 3 comment:2 by , 13 years ago
Replying to anevilyak:
Looks like an uninitialized pointer in the ports code somewhere...
Actually it looks like use of an already freed pointer. It's similar to the other port heap issues reported. Interestingly it actually ends up in 0xdeadbeef, which could now come from either heap implementation, the old heap still used by the port code, and the slab we currently use as kernel heap. Until now I thought there weren't any 0xdeadbeef's in those KDLs, so it may point at the slab, seeing that we only introduced 0xdeadbeef there last week.
comment:3 by , 13 years ago
comment:4 by , 11 years ago
Keywords: | port heap added; vm_page_fault 0xdeadbeef removed |
---|
comment:6 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
It's highly probable that this was fixed by hrev46290 or a related commit, as nobody seems to have seen it since.
comment:7 by , 5 years ago
Milestone: | R1 → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
KDL