Hi Sandeep,
On Mon, Sep 5, 2011 at 1:37 AM, sandeep kumar coolsandyfor...@gmail.com wrote:
...snip...
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'm not sure.
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
Hi :)
On Fri, Sep 2, 2011 at 13:03, sandeep kumar coolsandyfor...@gmail.com wrote:
Hi,
im working on android, kernel version 2.6.35.11
Briefly checking the dump, looks like it's ARM processor?
I got these logs showing kernel panic and the target is rebooting.
From the logs i understood in
Logs after enabling the CONFIG_DEBUG_USER and setting user_debug to 255, to
get more info(as suggested by Dave..)
3[ 89.663286] init: [boot time] processing action 0x4c5e8
(property:init.svc.samsungani=stopped)
3[ 89.663988] init: [boot time] processing action 0x4ef20
Hi Sandeep,
pls check 0xc92f which function is at this address ?
On Fri, Sep 2, 2011 at 4:41 PM, sandeep kumar coolsandyfor...@gmail.com wrote:
Logs after enabling the CONFIG_DEBUG_USER and setting user_debug to 255, to
get more info(as suggested by Dave..)
3[ 89.663286] init: [boot
Hi Sandeep,
On Fri, Sep 2, 2011 at 4:11 AM, sandeep kumar coolsandyfor...@gmail.com wrote:
Logs after enabling the CONFIG_DEBUG_USER and setting user_debug to 255, to
get more info(as suggested by Dave..)
3[ 89.663286] init: [boot time] processing action 0x4c5e8
