Opened 8 months ago

Closed 4 months ago

#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 8 months ago.
Screen Picture of kernel crash full kernel output here
kernel-crash-log-from syslog.txt (148.1 KB) - added by nedry 8 months ago.
Syslog output in TXT format of the kernel crash
syslog.good.txt (112.5 KB) - added by nedry 8 months ago.
Syslog after successful boot

Change History (8)

Changed 8 months ago by nedry

Attachment: IMG_0019.JPG added

Screen Picture of kernel crash full kernel output here

comment:1 Changed 8 months ago by mmlr

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 Changed 8 months ago by nedry

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 Changed 8 months ago by nedry

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?

Changed 8 months ago by nedry

Syslog output in TXT format of the kernel crash

comment:4 Changed 8 months ago by mmlr

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.

Changed 8 months ago by nedry

Attachment: syslog.good.txt added

Syslog after successful boot

comment:5 Changed 4 months ago by waddlesplash

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