kdb
[Top] [All Lists]

Re: [lkcd-general] kdb and lcrash

To: Ashok Raj <ashokr2@xxxxxxxxx>
Subject: Re: [lkcd-general] kdb and lcrash
From: Piet/Pete Delaney <piet@xxxxxxx>
Date: Tue, 26 Mar 2002 14:55:17 -0800
Cc: Piet Delaney <piet@xxxxxxx>, lkcd-general@xxxxxxxxxxxxxxxxxxxxx, tjm@xxxxxxx, kdb@xxxxxxxxxxx, Keith Owens <kaos@xxxxxxx>, Jack Steiner <steiner@xxxxxxx>, Jesse Barnes <jbarnes@xxxxxxx>
In-reply-to: <PPENJLMFIMGBGDDHEPBBKEBKCMAA.ashokr2@xxxxxxxxx>
References: <PPENJLMFIMGBGDDHEPBBKEBKCMAA.ashokr2@xxxxxxxxx>
Sender: owner-kdb@xxxxxxxxxxx
User-agent: Mutt/1.3.23i
On Tue, Mar 26, 2002 at 12:44:49PM -0800, Ashok Raj wrote:
> Hello.
> 
> Has anyone tried applying the kdb patch and the lkcd patch? i would like to
> be able to use the kernel debugger, and the crash at the same time. i.e on
> panic i would  like kdb to get control and have a command support to dump
> crash image if necessary.

I think we are experiencing a spinlock problem where kdb is stopping the
other CPU's and leaving a spinlock hung. I'll cc: you on the issue, if
anyone else is interested in the details let me know and I'll expand
the Cc: list.


I suspect the the kdb processing of:

        kdb(KDB_REASON_PANIC, 0, NULL)

may need something added to make sure spinlocks aren't being held. 

Perhaps we need to change kdb to behave more like:

        kdb(KDB_REASON_KEYBOARD, 0, (kdb_eframe_t)regs);

when we are using dump and kdb together.

Could also be a bug in lkcd, but curently it's only hanging on
systems with kdb installed.

-piet



<Prev in Thread] Current Thread [Next in Thread>
  • Re: [lkcd-general] kdb and lcrash, Piet/Pete Delaney <=