I am not sure this is the same problem:
I had the problem on ia64 where there is a conflict between kdb and
ia64 patch.
It depends on the order we apply the patches:
. kdb common patch then ia64 patch then kdb ia64 patch is OK.
. ia64 patch then kdb common patch & kdb ia64 patch: there is
a reject in init/main.c that prevents the call to kdb_init()
that file.
Xavier
David Douard writes:
> Hi !
>
> I'm not on the list so please CC me back.
>
> I'm using a 2.4.18 kernel (on a PIII (compaq Evo N150)) with latest ACPI
> patches (well this is why I need kdb... there is a acpi kdb module).
>
> I finally could compile everything, and when I hit the pause key, I go to
> kdb.
> It's fine BUT none standard commands are recognized !
> So I cannot type "go" : still have "Unknown command"... Quite annoying.
> I've seen something similar in a mail from Xavier Bru (january 2002)...
> Any kdb modules loaded are OK (acpi kdb seems to work fine. No intensive
> chech
> thou).
>
> So do you think it is the same pb reported by X.Bru (no init() called). And
> is
> there a simple solution ?
>
> Just a simple question (to which I can find the answer in the kernel, I
> know...) :
> when is the kdb_init function called ? At boot or when entering kdb ? (I
> guess
> at boot. Ok my question is quite stupid...)
> And then can I do debug printk in it ? (the awful debug method).
>
> Thank you.
>
> David Douard
|