Most of us who've used Linux for any significant length of time have had a kernel panic. Lately, those events have probably been while in X, making accessing the actual details of the event difficult if you haven't memorized the magic SysRq keys (assuming your kernel was compiled with the relevant support).
A couple workarounds are available to deal with this; You can set up a serial console so that system messages get dumped via good old RS-232 to another machine, or even a console on your parallel port so that the messages get printed.
Don't try that last unless you don't mind going through a ton of paper, and have ways of dealing with the printer noise.
It occurred to me, a few days ago, that x86 systems have a (very) small amount of non-volatile RAM, battery backed by the same battery that keeps your computer from losing time when you power cycle it.
While that amount of memory is very, very small, it may be large enough to hold a Panic message; That'd be a nice place for me to be able to look to investigate why my computer randomly hard-locked one evening while I was away.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment