On Tue, 26 Oct 2004 19:24:25 +0200,
Olaf Hering <[EMAIL PROTECTED]> wrote:
>
>Why is kdb call anyway if the system panics?
>If its off, it has to be off.
>
>diff -purN linux-2.6.5/kdb/kdbmain.c linux-2.6.5.kdb/kdb/kdbmain.c
>--- linux-2.6.5/kdb/kdbmain.c 2004-10-26 11:35:07.000000000 +0200
>+++ linux-2.6.5.kdb/kdb/kdbmain.c 2004-10-26 19:09:12.703683875 +02=
>00
>@@ -3810,6 +3810,8 @@ kdb_cmd_init(void)
> static int
> kdb_panic(struct notifier_block *self, unsigned long command, void *ptr)
> {
>+ if (!kdb_on)
>+ return 1;
> KDB_FLAG_SET(CATASTROPHIC); /* kernel state is dubious now */
> KDB_ENTER();
> return(0);
To allow for automatic lkcd dumps with clean data that is captured by
kdb. See linux/Documentation/kdb/dump.txt. kdb must be called so kdb
can decide if it will drop into the debugger, take a dump or return.
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
