Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 3 Jul 2007 12:47:02 +0300 | From | Jarkko Lavinen <> | Subject | Re: [PATCH/RFC] oops and panic message logging to MTD |
| |
On Tue, Jun 19, 2007 at 11:00:54AM +0100, Richard Purdie wrote: > Its not a case of formatting the whole partition. The whole point of > this code is the following use case: > > 1. Device crashes > 2. Device reboots > 3. mtdoops partition has a log of why it crashed
The oops logger uses oops_in_progress variable to detect the begin and the end of an oops. The end is detected when the first non-oops line comes and oops_in_progress is false.
This works if the kernel is still running after the oops and gemerates some non-oops messages. But if there is no non-oops line following an oops, no flushing will occur and there won't be a log on flash.
Jarkko Lavinen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |