NMI Interrupt introduced between r34760 and r34915

[adamk]

This afternoon I updated my local svn repo to hrev34915 and installed an updated build to a spare partition I use for testing.

Upon booting up, I'm greeted with a KDL: 'PANIC: Fatal exception "NMI Interrupt" occurred! Error code: 0x0" . I've noticed other reports on here, and someone on #haiku mentioned the same problem, but it seems that others are able to 'cont' and the boot up proceeds as normal. Unfortunately, continuing is not an option for me as I end up with a vm_page_fault.

I can still boot up my hrev34760 installation on another partition on the same drive.

I have a logging via a serial cable, and grabbed a backtrace which I am attaching to this ticket.

While it is certainly possible for me to start reverting to previous commits, this will undoubtedly take a while, so I'm hoping someone can read something in my backtrace that indicates the source of the problem and figure out which commit broke Haiku for me :-)

[adamk]

NMI Interrupt backtrace.

[adamk]

Successful boot of hrev34760

[adamk]

I've attached a log from a successful boot of the older version. The crash in the newer version seems to happen at about this point:

acpi: ACPI disabled ahci: ahci_supports_device

I get the ACPI disabled in the new buggy version, and then the crash occurs before the ahci line.

[anevilyak]

From the backtrace, looks possibly related to some of Ingo's recent area management changes...if that backtrace is consistent, the output of "call 15 -3" after the NMI itself would be interesting (i.e. without trying to continue).