analysis of kernel panic logs.
From: sandeep kumar <hidden>
Date: 2011-09-05 08:37:43
Hi Dave, I want to share what is the problem and how it got fixed. The problem goes like this, The init process(init.c) of ANDROID parses "init.rc" file which specifies the actions to be done on a specific trigger. In our case mistakenly we specified the trigger,but no action. Due to which the parser parsed the action to be NULL, and executed it when the trigger occured. Which caused the NULL dereferencing. We fixed that by doing a NULL check before calling the action. As our analysis for the problem goes, init being the critical process, when killed, platform called a system call to restart the kernel. is it correct or we missd something? I have the following questions also, 1) When we enabled that config option CONFIG_DEBUG_USER, the register dump we got, is of user space application, right? 2) init: unhandled page fault (11) at 0x00000000, code 0x80000007, this is given by the CONFIG_DEBUG_USER, any reference how to analyse the 'code' value? Thank you, Sandeep On Mon, Sep 5, 2011 at 1:26 PM, Dave Hylands [off-list ref] wrote:
Hi Sandeep, On Sun, Sep 4, 2011 at 10:51 PM, sandeep kumar [off-list ref] wrote:quoted
Hi Dave, The problem is solved. But i have one doubt.quoted
So the PC is 0, and the LR is C92F. That tells me that the code at C92F in your init process is trying to call a function through a NULL pointer. You can try disassembling your init process. Something likequoted
arm-eabi-objdump --disassemble initIn this case we came to know the process name 'init'. But in some cases we might just have the link register address, and no process name. say some user-space process has caused the panic. Can u tell me ..how to debug in that case?You should always have a pid & process name if its a user-space app which dies (at least if you enable CONFIG_DEBUG_USER and enabling user_debug) -- Dave Hylands Shuswap, BC, Canada http://www.davehylands.com
-- With regards, Sandeep Kumar Anantapalli, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110905/57f6ed75/attachment.html