On 09/11/2011 07:57 PM, lakehousetech wrote: > I'm currently working on porting gingerbread to a tablet (ARM MSM7k), > and the only way I know how to debug the boot process before adb starts > is by looking at the last_kmsg. Is there another way to determine why > servicemanager is being killed 4 times in 4 minutes? Even with loglevel > set to 8, the last_kmsg isn't very helpful.
I'm pretty sure last_kmsg just has the message in the kernel log buffer, not any messages from the Android logging system (which is also inside the kernel, but don't persist across a boot.) You might try either 1) shunting the android log messages into the kernel message buffer, so you can see them with last_kmsg, or 2) dumping the log messages into a file after the service manager is killed, but before the system hangs. For either of these, you should be able to put something into /init.rc using the local logcat command: 1) logcat -d >/dev/kmsg 2) logcat -d >/cache/logoutput-tmp.txt Note that 1 is likely to overrun the default kernel log buffer size. You can increase this by changing CONFIG_LOG_BUF_SHIFT and re-compiling your kernel. -- Tim ============================= Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment ============================= -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
