#4555: PANIC: Fatal Exception "NMI Interrupt" has occured -----------------------------+----------------------- Reporter: MasterNetra | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/alpha1 Resolution: | Keywords: NMI Blocked By: | Blocking: 8097 Has a Patch: 0 | Platform: x86 -----------------------------+----------------------- Comment (by mmlr): Replying to [comment:13 Duggan]: > Nope, that didn't do it :/ Ah well, at least that means it's not just some lingering error condition that triggers as soon as error reporting is enabled (or that our error reset doesn't actually work). I guess some more debug output is needed to determine what's going on exactly. In either case the error condition seems to come from the PCIe port that has the wired ethernet controller attached (PCI device 28 function 5 with secondary bus 8). From the data available alone it doesn't really look any different from the other PCIe ports... That reminds me though that the error condition clearing only every uses kprintf to output the data to the kernel debugger. What you could do when the NMI kicks in is execute the "pcistatus" KDL command, which should then list any present error conditions before trying to clear them. If you could attach that output (you can simply continue after executing that command) as well, that might give some clue. -- Ticket URL: <http://dev.haiku-os.org/ticket/4555#comment:14> Haiku <http://dev.haiku-os.org> Haiku - the operating system.