Re: Catching NForce2 lockup with NMI watchdog

[Bob <recbo@nishanet.com>]

Maciej W. Rozycki wrote:

>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...................
>>NMI:          0...........
>>
> 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.
>
>  
>
Using a patch that fixes a number of people's nforce2
lockups while enabling io-apic edge timer, I can now
use nmi_watchdog=2 but not =1

turn on ioapic edge timer--

http://www.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/broken-out/nforce2-apic.patch

We're all trying to get acpi, apic, lapic, io-apic working
when turned on in cmos/bios and kernel.

The three things that each alone have achieved stability
on somebody's system here are 1) bios update 2) cpu
disconnect off either in cmos if available or by athcool
or kernel patch with same 3) timing delay patch

For CPU disconnect you still need athcool or this one
http://www.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/broken-out/nforce2-disconnect-quirk.patch 


Both patches are for 2.6.0-test11 kernel.