Re: oops on reboot damaged filesystem

[Keith Owens <kaos@melbourne.sgi.com>]

On Tue, 21 Aug 2001 09:01:32 +1200, 
"Godfrey Livingstone" <godfrey.livingstone@ajpark.co.nz> wrote:
>How do you save an oops and kdb output, does issuing DEBUG=1 when in kdb
>save the output or is that unnecessary?

"set LOGGING=1" in kdb to log the output to disk, via syslog.  But that
only works if the kernel can recover after the oops, if the machine
dies then syslog never gets called.  Your best option is to use a
serial console, Documentation/serial-console.txt, and capture the
serial output on the second machine.

>Is the output from the kbd bt command needed? 

Depends on the type of error.  For a deadlock, bt is useful.  For a
straight oops, it is rarely useful, unless the oops comes from code
that is testing for deadlocks.