> On many systems, you can find memory that isn't zeroed by the BIOS
> on boot. I have a patch that saves the console log into such memory
> as it gets written -- this lets you get to the oops after the
> reboot.
Well, my solution is to put 10sec pause after oops - so that you can
copy it by hand :-).
If that is not enough, you can go for Nowell-like solution:
Kernel oopsed, please insert blank formatted floppy and press Magic-d
(then 60 seconds pause and then system tries to contiue or tries to reboot)
:-) But serial line works much better.
It is bad idea to write post-oops dump onto hdd, but writting onto fdd
is not _that_ risky.
-- I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!- 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/