Openmoko Bug #2135: write kernel crash message somewhere where it can be retrieved after reboot?

[Openmoko Public Trac]

#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel     
     Type:  enhancement      |         Status:  new                 
 Priority:  high             |      Milestone:  stable-kernel-2009.1
Component:  System Software  |        Version:  unspecified         
 Severity:  normal           |       Keywords:                      
 Haspatch:  0                |      Blockedby:                      
Estimated:                   |    Patchreview:                      
 Blocking:                   |   Reproducible:                      
-----------------------------+----------------------------------------------

Comment(by lindi):

 Inspired by werner's poke.c I wrote a userland tool to dump the contents
 of the ramconsole via /dev/mem -- http://iki.fi/lindi/openmoko/ramconsole-
 dump.c

 I then modified the ramconsole patch so that it does not need to print the
 contents of the ramconsole on bootup. This fixes issues #3, #4, #5 and #6.
 (#6 is fixed since now the policy to discard corrupted ramconsole header
 is in userland and can be changed if somebody needs to recover partially
 corrupted data manually).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac