kdb
[Top] [All Lists]

Re: KDB hang

To: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Subject: Re: KDB hang
From: "Juan J. Quintela" <quintela@xxxxxxxxx>
Date: 03 Oct 2000 13:09:10 +0200
Cc: kdb@xxxxxxxxxxx
In-reply-to: Keith Owens's message of "Tue, 03 Oct 2000 12:52:53 +1100"
References: <2558.970537973@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-kdb@xxxxxxxxxxx
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
>>>>> "keith" == Keith Owens <kaos@xxxxxxxxxxxxxxxxx> writes:

keith> On 03 Oct 2000 03:21:09 +0200, 
keith> "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????

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

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

bta, and yes I was trying to make sense for a backtrace (i.e. not
continuing pressing keys).  This has worked for ages (i.e. kdb
1.[34]).

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

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