Opened 11 years ago

Closed 8 years ago

#2680 closed bug (fixed)

Panic on boot: Fatal exception "NMI Interrupt" occurred!

Reported by: clebin Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc: marcusoverhagen
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Haiku gives me a kernel panic as it boots, even with all the safe mode options selected.

I'm building directly to a partition from Ubuntu, which worked up until around 4 months ago. I can build to a raw image and boot it in Qemu ok. My hardware is a Fujitsu-Siemens Amilo PI 1505 - Core Duo, Intel GMA 950 graphics, Intel HDA sound, SATA, Firewire... (technical spec attached)

I've attached a back-trace. Let me know if you need anything else (hope I didn't duplicate any bug here...)

Attachments (3)

backtrace.JPG (135.2 KB) - added by clebin 11 years ago.
Backtrace
pi1505_specification.pdf (59.8 KB) - added by clebin 11 years ago.
Laptop specs
backtrace2.JPG (118.4 KB) - added by clebin 11 years ago.
Backrace after removing fw_raw

Download all attachments as: .zip

Change History (15)

Changed 11 years ago by clebin

Attachment: backtrace.JPG added

Backtrace

Changed 11 years ago by clebin

Attachment: pi1505_specification.pdf added

Laptop specs

comment:1 Changed 11 years ago by koki

Cc: kokitomare@… added

This sounds similar to bug #2243.

(A workaround for #2243 is to remove the Firewire driver; you may want to try that).

comment:2 in reply to:  1 Changed 11 years ago by clebin

Replying to koki:

This sounds similar to bug #2243.

(A workaround for #2243 is to remove the Firewire driver; you may want to try that).

Doesn't seem to work for me.

Pardon my ignorance - I deleted the firewire folder containing fw_raw from the src and generated folders and ran 'jam -q', then 'sudo jam -q' again.

Changed 11 years ago by clebin

Attachment: backtrace2.JPG added

Backrace after removing fw_raw

comment:3 Changed 11 years ago by umccullough

Component: - GeneralDrivers

I'm pretty sure just deleting the source directory would just end up causing the jam to fail (and not write a new image to the partition at all).

The proper way to remove a target from the image is to edit build/jam/HaikuImage and remove the targets there.

Line's 140 and 181 it appears

http://dev.haiku-os.org/browser/haiku/trunk/build/jam/HaikuImage#L140

and

http://dev.haiku-os.org/browser/haiku/trunk/build/jam/HaikuImage#L181

That said, it may still not be firewire related even if it demonstrates the same bug - AFAICT, the firewire issue reported in the other ticket exposes some kind of flaky hardware issue that isn't that common.

comment:4 Changed 11 years ago by clebin

That didn't work either, sadly.

I know within a month or so when Haiku stopped booting on my hardware. It may be possible for me to roll back and fore on SVN to locate the first broken revision.

comment:5 in reply to:  4 Changed 11 years ago by absabs

Replying to clebin:

That didn't work either, sadly.

I know within a month or so when Haiku stopped booting on my hardware. >It may be possible for me to roll back and fore on SVN to locate the first >broken revision.

Where is the backtrace jpg? I can't see it. As for NMI panic, there is a similar problem with some buggy firewire pci cards. But just type continue when KDLed, everything will OK. Perhaps other pci hardware can panic too. Have you tried under Linux? IIRC, the buggy firewire pci card will panic the linux kernel too when /proc/sys/kernel/panic_on_unrecovered_nmi is set to one.

comment:6 Changed 10 years ago by oco

Component: DriversSystem/Kernel

My laptop experience this problem too. "continue" in the kernel debugger always work and then Haiku boot fine. If it could help, someone could take a look at my laptop here at BeGeistert. My laptop is an aspire 1513 LMI (AMD64).

comment:7 Changed 10 years ago by Joris_m

I am trying to boot haiku from a USB key on a fujitsu siemens amilo laptop (XI 2528). I encounter the same problem during boot. However when I type continue I see the led next to the USB port go out and than everything hangs.

Best regards,

Joris_M

comment:8 Changed 10 years ago by marcusoverhagen

Cc: marcusoverhagen added

comment:9 Changed 9 years ago by scottmc

clebin, can you retry this using the alpha, and if that still fails report back here, and also try a more recent version as well, as there's been quite a bit of work done since the alpha release.

comment:10 Changed 8 years ago by scottmc

Is anyone still seeing this issue? If not then I'll close this one out soon as it's probably been fixed sometime in the past 2 years. My laptop with firewire has no booting issues.

comment:11 Changed 8 years ago by anevilyak

Wasn't this one "solved" by removing the firewire driver?

comment:12 Changed 8 years ago by scottmc

Resolution: fixed
Status: newclosed

closing this as it's probably been fixed.

Note: See TracTickets for help on using tickets.