#14046 closed bug (duplicate)

PANIC: vm_page_fault: unhanded page fault in kernel space

Reported by: nedry Owned by: nobody
Priority: critical Milestone: Unscheduled
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: #14182 Blocking:
Has a Patch: no Platform: x86

Description

Hello during powering on an Thinkpad T40 2gb ram running Haiku Walter (Revision hrev51856) with Ethernet plugged in i get the following kernel error: PANIC: vm_page_fault: unhanded page fault in kernel space

Attachments (3)

IMG_0019.JPG (1.8 MB ) - added by nedry 17 months ago.
Screen Picture of kernel crash full kernel output here
kernel-crash-log-from syslog.txt (148.1 KB ) - added by nedry 17 months ago.
Syslog output in TXT format of the kernel crash
syslog.good.txt (112.5 KB ) - added by nedry 17 months ago.
Syslog after successful boot

Change History (8)

by nedry, 17 months ago

Attachment: IMG_0019.JPG added

Screen Picture of kernel crash full kernel output here

comment:1 by mmlr, 17 months ago

It may work to type the syslog command at the KDL prompt to see a bit of context. Can you try that and post pictures of the last couple of screens of the output? It's apparently a null pointer access in the ipro1000 driver and I'd be interested to know if it there's any prior output.

comment:2 by nedry, 17 months ago

Hi i grabbed the screen shot and rebooted and not see it again, i will try again tomorrow to see if it does it again and if it does then will send you a screen shot.

comment:3 by nedry, 17 months ago

OK tried again today, and it crashed again, i did a syslog and lots of data came up, i did photo it, however even compressing the photos comes to 44mb do you want it? is there somewhere you want me to upload them to?

by nedry, 17 months ago

Syslog output in TXT format of the kernel crash

comment:4 by mmlr, 17 months ago

Thanks! The text log is all that's needed, sorry for instructing to take photos.

Since it doesn't always happen, it'd be interesting to also get a syslog from a successful boot for comparison. It can be found in /var/log/syslog after booting.

To me it intuitively looks like the handler is called early, i.e. before everything is fully initialized. I'd expect some more debug output from the driver, a successful syslog may show that.

by nedry, 17 months ago

Attachment: syslog.good.txt added

Syslog after successful boot

comment:5 by waddlesplash, 14 months ago

Blocked By: 14182 added
Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.