Oops in flash

[Guennadi Liakhovetski]

Hello

There once was a patch to the kernel to save Oops to diskets. I've done a
similar thing - for flash. You just reserve a small (smallest, normally,
128K) partition on flash and, when an Oops happens, it is just written to
it. Reasoning is simple - one can't always attach a serial console to all
systems, and not all bugs are so simple to reproduce. Then one could
write an init-script co check this partition, and if it not clean - save
contents and erase.

The patch is small and simple, one just has to find a suitable place for
it. Also, we don't set the oops_in_progress variable on ARM - it can be
quite nicely used for this purpose. Should we do it regardless?

If there is interest, I could clean it up and send to the list, although,
it is really trivial.

CC-ing to LKML, because other embedded (and not so embedded) systems might
also find this idea useful.

Yes, it is not so simple, if the oops happens in or during another access
to flash - I don't handle this...

Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany


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