* Ed Tomlinson <[EMAIL PROTECTED]> wrote:
> >> - if yes, does booting with "nmi_watchdog=2 idle=poll" give you a
> >> working NMI watchdog? (working NMI watchdog means the NMI counts
> >> increase for all cores in /proc/interrupts).
>
> > booting with the above gives me an incrementing NMI counter in
> > /proc/interrupts
>
> Ingo,
>
> Is there anything else that needs to be set in the kernel config for
> the nmi watchdog to trigger?
>
> I ask because I just had a hang but nothing showed on the _serial_
> console - I waited a couple of minutes before rebooting.... Is there
> any other way to verify the watchdog is working?
if you cause a hard lockup intentionally via an infinite irqs-off loop:
# cat > lockupcli.c
main ()
{
iopl(3);
for (;;) asm("cli");
}
Ctrl-D
make lockupcli
./lockupcli
does the NMI watchdog properly trigger? If not, does booting with
idle=poll change the situation?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
