Messages in this thread | | | Date | Tue, 9 Dec 2003 15:21:30 +0100 (CET) | From | "Maciej W. Rozycki" <> | Subject | Re: Catching NForce2 lockup with NMI watchdog |
| |
On Sun, 7 Dec 2003, Bob wrote:
> I have append="nmi_watchdog=1" ? Nothing "nmi" or "NMI" is logged. > > cat /proc/interrupts > CPU0 > 0: 241105839 XT-PIC timer > 1: 27337 IO-APIC-edge i8042 > 2: 0 XT-PIC cascade > 8: 1 IO-APIC-edge rtc > 9: 0 IO-APIC-level acpi > 12: 217952 IO-APIC-edge i8042 > 14: 22 IO-APIC-edge ide0 > 15: 24 IO-APIC-edge ide1 > 16: 4245875 IO-APIC-level 3ware Storage Controller, yenta, yenta > 17: 5428737 IO-APIC-level eth0 > 21: 0 IO-APIC-level NVidia nForce2 > NMI: 0 > LOC: 241091187 > ERR: 0 > MIS: 6
You don't have the NMI watchdog working, because the timer interrupt is configured as an 8259A interrupt ("XT-PIC" for IRQ 0 in the output above). This usually means the wiring of a particular system doesn't provide any other alternative or configuration data provided by the BIOS is broken. The timer interrupt has to be configured as an I/O APIC interrupt for the watchdog to work, or you can select "nmi_watchdog=2" for an alternative watchdog internal to processors if they support it.
-- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available + - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |