Francesco de Virgilio <[email protected]> writes: > Is it related with CPU overload or something similar? Is it related with > kernel version (a suggested super-stable kernel?)? Is there a way to > read in the logs which is the cause of this problem?
Add "panic=15" to kernel command line to have it automatically reboot on panic. modprobe s3c2410_wdt and configure watchdogd to reboot the system if it is not responding. Patch the kernel with http://docs.openmoko.org/trac/attachment/ticket/2135/ramconsole-1.patch to have kernel logs persist over reboot. _______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
