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

Openmoko Public Trac bugs at docs.openmoko.org
Tue Jan 27 01:36:18 CET 2009


#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 andy):

 It's cool you got this working :-)  I guess you already quite aware of it
 but we need to decrease the footprint in kernel.c and move all the magic
 addresses to mach-gta02.c.

 It can do with a KConfig to enable it for compile.  Rather than mem=, we
 can eventually screw with the ATAG for valid physical RAM extent in Qi so
 we don't have to burn a whole megabyte.

 Also we could do with protecting at least the metadata struct info with a
 hash or crc so we know we can trust it on reboot, and some error checking
 there.

 But I realize you only just got the whole cycle working :-)  Nice work!

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


More information about the openmoko-kernel mailing list