On Tue, 24 Apr 2001 09:54:28 -0700,
"Matt D. Robinson" <yakker@xxxxxxxxxxxxxx> wrote:
>Normally, KDB will be invoked first, and then when you exit KDB,
>the system should panic. They were intended (at least they were
>two years ago) to be daisy chained, one after the other. The
>only issue is making sure KDB leaves the system in a decent state
>so a system crash can occur.
>
>There should be no issue in ordering, unless Keith changed something
>in how KDB is invoked.
The only recent change is that kdb now gets control from panic, via
panic_notifier_list, this was added because people complained that kdb
was not being invoked for explicit kernel panics. So you might see kdb
being entered twice, once for the initial oops and again for the kernel
panic. Typing 'go' twice should get you to the next panic routine.
If it does not work, let me know.
|