kdb
[Top] [All Lists]

Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5

To: Keith Owens <kaos@xxxxxxx>
Subject: Re: using kdb on Red Hat/SGI linux-2.4.18-18SGI_XFS_1.2pre5
From: "Foris, Jim (MED)" <foris@xxxxxxxxxxxxxxxx>
Date: Thu, 06 Feb 2003 17:22:25 -0600
Cc: "Foris, Jim (MED)" <foris@xxxxxxxxxxxxx>, kdb@xxxxxxxxxxx
In-reply-to: <21932.1044571843@xxxxxxxxxxxxxxxxxxxxx>
References: <21932.1044571843@xxxxxxxxxxxxxxxxxxxxx>
Sender: kdb-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218
Keith Owens wrote:
On Thu, 06 Feb 2003 16:33:43 -0600, "Foris, Jim (MED)" <foris@xxxxxxxxxxxxxxxx> wrote:

Second, I am not able to break into a system hang - making the debugger
useless for what I really need it for.


Use the nmi watchdog, boot with nmi_watchdog=1.


Did that... made no difference.

We think it is because CPU0 handles all NMIs.... so if it dies,
so does the NMI watchdog.


Is there anything I need to do special to get symbols in the KDB tracebacks
(like configure in stack frame pointers, maybe?) ?


kallsyms is automatically included.  What does your backtrace look like?


Here is a section from a crash:


[1]kdb> bt
ESP        EIP        Function (args)
0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
                               kernel <unknown> 0x0 0x0 0x0
0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
                               kernel <unknown> 0x0 0x0 0x0



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