Knowledge BaseThe Digium Knowledge Base is a searchable library of troubleshooting advice and current information updated by Digium support technicians. |
Knowledge Base / Hardware /
Why do I get an NMI error? |
|
|
NMI errors come from the kernel. An NMI is a (N)on (M)askable (I)nterrupt. They can be caused by various parts of the system, and they usually occur when there are really basic hardware problems (i.e., memory errors, chipset problems, etc.). Normal interrupts (i.e., interrupts from peripheral/non-core devices) are maskable, but NMIs exist when there is a problem that is so basic that the system absolutely has to catch it (such as for really basic component errors, etc). When an NMI occurs in Linux, it is handled by the architecture-dependent code (i386 in your case) of the kernel (i.e. Not the Zaptel drivers). Update to the latest Zaptel code version to resolve NMI errors. If the latest Zaptel version does not resolve the issue try disabling the NMI watchdog option to resolve /proc/interrupts from reporting NMI's. Specify nmi_watchdog=0 as a kernel argument at boot time. You may also try disabling APIC by specifying "noapic", without quotes, as a kernel argument at boot time. You may also want to try the following at kernel boot time in order to help resolve NMI errors: "nmi_watchdog=0 pci=norouteirq acpi=off pci=noacpi noapic." |
|
Powered by KBPublisher (Knowledge base software)