[PATCH] RFC: don't aggravate kernel panics

Andy Green andy at openmoko.com
Tue Jan 20 16:16:14 CET 2009

Hash: SHA1

Somebody in the thread at some point said:

|> Another way to come at that would be stash the syslog somewhere safe
|> near the end of memory, set a signature there and reboot off the panic
|> into the recovery kernel, and show it there.
| We could just always copy the dmesg buffer to a safe place on panic
| or such and do a normal reboot. As long as we make sure the DRAM
| gets refreshed, then the next system, which doesn't even have to be
| anything special, can just pick it up.

You just repeated exactly what you quoted from what I wrote :-)

| Apropos recovery system, are you thinking of a "connect to Internet
| and mail crash log to Andy" button in the extended boot loader ? ;-))

It'd be enough if it displays it and saves it to SD Card where it can be
recovered at will, it's a long way ahead of where we are today if the
user doesn't have a debug board.  It also covers the case where Qi can't
start due to rootfs issue, the kernel will panic and the user can see why.

But we should set a flag or erase the panic dump after dumping it once,
otherwise if the backup rootfs has trouble it'll just loop :-)

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list