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 12:37:54 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:                 
-----------------------------+----------------------------------------------
 This is a wishlist bug. Would it be possible to write the kernel crash
 message somewhere where it can be retrieved after reboot? Would writing to
 nand (to dedicated partition) be safe? If uboot does not overwrite RAM
 contents could the error be retrieved from RAM after reboot?

 If this fails it should be quite easy to send the contents of the panic
 message by blinking the AUX led, right? The only problem here is that
 there needs to be some automated way to capture it.

 Audio would be easier to capture since people have soundcards to record it
 but it would probably be harder to control when the kernel has crashed
 (and it would annoy everyone around you while you are booting your laptop
 to capture the crash message :P).

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


More information about the openmoko-kernel mailing list