kdb
[Top] [All Lists]

Re: KDB hang

To: "Juan J. Quintela" <quintela@xxxxxxxxx>
Subject: Re: KDB hang
From: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Tue, 03 Oct 2000 12:52:53 +1100
Cc: kdb@xxxxxxxxxxx
In-reply-to: Your message of "03 Oct 2000 03:21:09 +0200." <yttpulioh2y.fsf@xxxxxxxxxxxx>
Sender: owner-kdb@xxxxxxxxxxx
On 03 Oct 2000 03:21:09 +0200, 
"Juan J. Quintela" <quintela@xxxxxxxxx> 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:"?


<Prev in Thread] Current Thread [Next in Thread>