NMI is non-maskable interrupt. It is usually caused by a memory parity
error.
The obvious question is, has the memory been thoroughly tested or
alternative known-good modules been tried. The linkage to devices tends
to indicate RAM is fine but it would be good if we could authoritatively
rule it out.
The alternative is that the devices are somehow messing with the system
bus.
The kernel handles it in
arch/x86/kernel/traps.c::mem_parity_error():
{
printk(KERN_EMERG
"Uhhuh. NMI received for unknown reason %02x on CPU %d.\n",
reason, smp_processor_id());
printk(KERN_EMERG
"You have some hardware problem, likely on the PCI bus.\n");
#if defined(CONFIG_EDAC)
if (edac_handler_set()) {
edac_atomic_assert_error();
return;
}
#endif
if (panic_on_unrecovered_nmi)
panic("NMI: Not continuing");
printk(KERN_EMERG "Dazed and confused, but trying to
continue\n");
/* Clear and disable the memory parity error line. */
reason = (reason & 0xf) | 4;
outb(reason, 0x61);
}
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Incomplete => In Progress
--
NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
