Openmoko Bug #2135: write kernel crash message somewhere where it can be retrieved after reboot?
Openmoko Public Trac
bugs at docs.openmoko.org
Wed Nov 26 13:18:19 CET 2008
#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
I would use RAM. It's easy to access and it's very likely to survive a
reset. Also, since the kernel itself may not know it is dead (e.g., if
the system just hangs and you have to reset it), you would want to write
all messages to that "safe" location, so access should be inexpensive.
For retrieval, you could either extend the boot loader, or, better, only
start writing to the "safe area" after you've checked for the presence
of old content. That way, crashes occurring before the retrieval could
not be recorded (if you use multiple buffers you rotate, you could even
handle some cases, but it may not be worth the effort), but you're
probably after those that are hard to reproduce and only happen after a
while.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list