![]() | |||||||||||||
Messages in this thread
|
* Ingo Molnar <mingo@elte.hu> wrote: > the NMI watchdog warning is a bit weird: > > Calling initcall 0xc0613e4f: check_nmi_watchdog+0x0/0x1a8() > Testing NMI watchdog ... CPU#0: NMI appears to be stuck (0->0)! > CPU#1: NMI appears to be stuck (0->0)! > initcall 0xc0613e4f: check_nmi_watchdog+0x0/0x1a8() returned -1. > initcall 0xc0613e4f ran for 27 msecs: check_nmi_watchdog+0x0/0x1a8() > > i'll test it in a minute with that turned off. yeah, with nmi_watchdog=0 it works fine. nmi_watchdog=2 always worked on this box so this is some new regression. Ingo - 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: 2007-06-05 09:21 [W:1.181 / U:1.010 seconds] ©2003-2008 Jasper Spaans | |||||||||||||