On Fri, 19 Mar 2004 09:20:36 +0000 (GMT),
=?iso-8859-1?q?SAROJ=20DAS?= <saroj_d@xxxxxxxxx> wrote:
>I am finding difficulty in capturing KDB output. I can
>display and see results while still in KDB. But once I
>am out from KDB it's all gone.
>I went thru the mailing list and found Kleith Owens
>answer in this line. The answer says to set LOGGING=1.
>I tried the same in KDB as well as system command
>prompt, but still, unsuccessful. Is there anyting I am
>missing?
set LOGGING=1 will log the kdb output to syslog but only (a) after you
type 'go' to exit kdb so the rest of the kernel can run and (b) the
kernel is well enough to write data to syslog. In many cases, the
kernel is failing so badly that it cannot write data to syslog or disk,
so the logging never gets saved by the kernel.
The alternative is to compile the kernel with a serial console, reboot
pointing the console at a serial port, run a null modem to a second
machine which is running a terminal emulator such as minicom and
capture the debug output on the terminal emulator. See
Documentation/serial-console.txt.
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
|