kdb
[Top] [All Lists]

RE: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked dir

Subject: RE: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB....
From: "Bruce Edge" <bedge@xxxxxxxxxxxxxxxxxx>
Date: Tue, 16 Dec 2003 09:15:48 -0800
Cc: <lkcd-general@xxxxxxxxxxxxxxxxxxxxx>, <kdb@xxxxxxxxxxx>
Sender: kdb-bounce@xxxxxxxxxxx
Thread-index: AcPDcARr6N3gysnhSD+Cn/eDiLuL0wAh1/yQ
Thread-topic: FW: [lkcd-general] This kernel supports KDB but LKCD was invoked directly, not via KDB....
> -----Original Message-----
> From: Keith Owens [mailto:kaos@xxxxxxxxxx]
> 
> On Mon, 15 Dec 2003 16:40:30 -0800, 
> "Bruce Edge" <bedge@xxxxxxxxxxxxxxxxxx> wrote:
> 
> >I get it when I load a module that does a divide by zero:
> >Code: f7 fb 89 c1 a1 10 c3 d2 c2 8b 00 83 e0 0f 83 f8 03 76 23 83=20
> >This kernel supports KDB but LKCD was invoked directly, not via KDB.
> >Falling back to the old and broken LKCD method of getting 
> data from all cpus,
> >do not be surprised if LKCD hangs.
> 
> You have a misapplied patch to arch/i386/kernel/traps.c.

[snip example]

Yup, that was it, patch went in crooked.

I tried applying the kdb and lkcd patches in different orders, and there's no 
one order that works cleanly.
Seems like there ought to be a combined lkcd/kdb patch since these two entities 
work so closely together, especially in light of the fact that the kdb readme 
contains an additional patch for lkcd.
Although, that's just one more thing to test that no-one ever has time for.

Thanks for your help.

-Bruce

Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>