![]() | |||||||||||||
Messages in this thread |
On Sat, 13 Mar 2004 22:42:55 +0100, Joerg Sommrey wrote: >in my box (Tyan Tiger MPX / 2x AMD Athlon) the NMI watchdog never worked >on any kernel that I tried (2.4.x, 2.6.x). I always found: >| activating NMI Watchdog ... done. >| testing NMI watchdog ... CPU#0: NMI appears to be stuck! > >But there is one exception: 2.6.3-mm4 shows: >| activating NMI Watchdog ... done. >| testing NMI watchdog ... OK. > >[2.6.3-mm4 was the only -mmX kernel I tried so far.] > >With 2.6.4-mm1 the NMI watchdog is again not functional in my box. Any >ideas? Insufficient data. Please try a standard 2.6.4 or 2.4.25 kernel and provide the complete dmesg boot log and the .config used. nmi_watchdog=1 may be broken on some chipsets, but nmi_watchdog=2 should work, at least in a standard kernel with oprofile disabled. /Mikael - 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 13:01 [from the cache] ©2003-2008 | |||||||||||||