lkml.org 
[lkml]   [2003]   [Dec]   [5]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 5 Dec 2003 08:40:58 +0100
FromMikael Pettersson <>
SubjectRe: Catching NForce2 lockup with NMI watchdog
Jesse Allen writes:
 > Hi,
 > 
 > I have a NForce2 board and can easily reproduce a lockup with grep on an IDE 
 > hard disk at UDMA 100.  The lockup occurs when both Local APIC + IO-APIC are 
 > enabled.  It was suggested to me to use NMI watchdog to catch it.  However, the 
 > NMI watchdog doesn't seem to work.
 > 
 > When I set the kernel parameter "nmi_watchdog=1" I get this message in 
 > /var/log/syslog:
 > Dec  4 20:10:30 tesore kernel: ..MP-BIOS bug: 8254 timer not connected to 
 > IO-APIC
 > Dec  4 20:10:30 tesore kernel: timer doesn't work through the IO-APIC - 
 > disabling NMI Watchdog!
 > 
 > "nmi_watchdog=2" seems to work at first, In /var/log/messages:
 > Dec  4 20:13:11 tesore kernel: testing NMI watchdog ... OK.
 > but it still locks up.

The NMI watchdog can only handle software lockups, since it relies on
the CPU, and for nmi_watchdog=1 the I/O-APIC + bus, still running.
Hardware lockups result in, well, hardware lockups :-(
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:59    [from the cache]
©2003-2008