KDB hang

Keith Owens kaos at melbourne.sgi.com
Mon Oct 2 18:52:53 PDT 2000


On 03 Oct 2000 03:21:09 +0200, 
"Juan J. Quintela" <quintela at fi.udc.es> wrote:
>        using kbd-1.5 (final) with test9-pre9 I have got 
>
>Enter <q> to end, <cr> to continue:
>NMI Watchdog detected LOCKUP on CPU1, regist: CPU:    1
>
>That happened while playing with the debugger in an SMP system.  Could
>be that you forgot to deactivate the NMI watchdog at kdb entry????

The NMI watchdog is not deactivated.  Instead there is a kdb state flag
which says to ignore the NMI watchdog tick.  This state bit is twiddled
in several places, it is turned on in main kdb, it is turned off during
a kdb command (to catch loops in commands), it should be turned on
again when waiting for input.  Looks like the state is incorrect.

Which command did you issue that generated "Enter <q> to end, <cr> to
continue:"?




More information about the kdb mailing list