Re: OOPS problems

Rogier Wolff (R.E.Wolff@BitWizard.nl)
Mon, 4 Jan 1999 11:18:36 +0100 (MET)

J. S. Connell wrote:
> > > But if klogd or syslogd are not running then the Oops never gets
> > > written to disk. Alas this occurs all too often.
>
> Or if your /etc/syslog.conf has not been told to log kern.*, or if the
> logfile it's written to is written non-synchronously and your machine
> immediately crashes, or if the panic takes out the filesystem driver for
> /var/log's partition, or if the disk driver panics, or ...

There are two kinds of Oopses. One that simply kill the offending
process, and the system continues. The other simply hangs the machine
because "nothing more can be done". Usually "killing interrupt handler,
killing idle task", and then "game over".

This last type is the one where klogd and syslogd try to log
synchronously, but don't get a chance.

Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
*   Never blow in a cat's ear because if you do, usually after three or  *
*   four times, they will bite your lips!  And they don't let go for at  *
*   least a minute. -- Lisa Coburn, age 9


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/