Re: 2.1.129 Crash, part of /var/log/messages attached

Matthias Urlichs (smurf@noris.de)
27 Nov 1998 12:41:25 +0100

alan@lxorguk.ukuu.org.uk (Alan Cox) writes:
> The first oops is as a result of some kind of serious memory corruption
> origin not clear, the rest of the data hasnt been run through ksymoops
> so isnt useful.
>
There might be a case for klogd "I see an Oops => log it, sync the file,
THEN decode it, sync the file again, do a hard reboot".

Just so that fuckups like this one don't cause a data loss avalance.

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661


-
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/