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 (property:init.svc.samsungani=stopped) <7>[ 89.664049] init: unhandled page fault (11) at 0x00000000, code 0x80000007 <1>[ 89.664080] pgd = de370000 <1>[ 89.664110] [00000000] *pgd=5eb83031, *pte=00000000, *ppte=00000000 <4>[ 89.664141] <4>[ 89.664171] Pid: 1, comm: init <4>[ 89.664202] CPU: 1 Not tainted (2.6.35.11 #4) <4>[ 89.664232] PC is at 0x0 <4>[ 89.664232] LR is at 0xc92f <4>[ 89.664263] pc : [<00000000>] lr : [<0000c92f>] psr: 60000010 <4>[ 89.664293] sp : bebb5e70 ip : ffffff88 fp : 00000000 <4>[ 89.664324] r10: 0003777c r9 : 00000001 r8 : 00000001 <4>[ 89.664355] r7 : 0003777c r6 : bebb5e94 r5 : 00000000 r4 : 0003777c <4>[ 89.664385] r3 : 00000000 r2 : 0004ef40 r1 : 0004ef50 r0 : 00000033 <4>[ 89.664446] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user <4>[ 89.664477] Control: 10c57c7d Table: 5e77006a DAC: 00000015 <0>[ 89.664660] Kernel panic - not syncing: Attempted to kill init! <4>[ 89.664721] [<c01076b8>] (unwind_backtrace+0x0/0x164) from [<c072436c>] (panic+0x6c/0xec) <4>[ 89.664782] [<c072436c>] (panic+0x6c/0xec) from [<c01a931c>] (do_exit+0x70/0x6a0) <4>[ 89.664812] [<c01a931c>] (do_exit+0x70/0x6a0) from [<c01a99dc>] (do_group_exit+0x90/0xc0) <4>[ 89.664873] [<c01a99dc>] (do_group_exit+0x90/0xc0) from [<c01b8fc4>] (get_signal_to_deliver+0x3e0/0x424) <4>[ 89.664934] [<c01b8fc4>] (get_signal_to_deliver+0x3e0/0x424) from [<c01039d8>] (do_signal+0x68/0x640) <4>[ 89.664995] [<c01039d8>] (do_signal+0x68/0x640) from [<c0103fc8>] (do_notify_resume+0x18/0x38) <4>[ 89.665056] [<c0103fc8>] (do_notify_resume+0x18/0x38) from [<c0100bd0>] (work_pending+0x1c/0x20) <2>[ 89.665117] CPU0: stopping <0>[ 89.665117] Rebooting in 5 seconds..[<c01076b8>] (unwind_backtrace+0x0/0x164) from [<c0100334>] (do_IPI+0xd8/0x154) <4>[ 89.665178] [<c0100334>] (do_IPI+0xd8/0x154) from [<c0727f4c>] (__irq_svc+0x4c/0xe4) <4>[ 89.665240] Exception stack(0xdc02fd90 to 0xdc02fdd8) <4>[ 89.665270] fd80: c1bd34a0 ffffffff c1bd34a8 40100068 <4>[ 89.665301] fda0: c1bd34a0 dcd060b0 00000008 761945df c1bd34a0 ddd5ac90 00000001 77fa555f <4>[ 89.665362] fdc0: 00000001 dc02fdd8 c0221558 c0213e68 20000113 ffffffff <4>[ 89.665423] [<c0727f4c>] (__irq_svc+0x4c/0xe4) from [<c0213e68>] (put_page+0xc/0x120) <4>[ 89.665453] [<c0213e68>] (put_page+0xc/0x120) from [<c0221558>] (do_wp_page+0x5fc/0x6f4) <4>[ 89.665514] [<c0221558>] (do_wp_page+0x5fc/0x6f4) from [<c0221fe0>] (handle_mm_fault+0x66c/0x718) <4>[ 89.665575] [<c0221fe0>] (handle_mm_fault+0x66c/0x718) from [<c0729e40>] (do_page_fault+0x190/0x35c) <4>[ 89.665636] [<c0729e40>] (do_page_fault+0x190/0x35c) from [<c01004f8>] (do_DataAbort+0x34/0x94) <4>[ 89.665667] [<c01004f8>] (do_DataAbort+0x34/0x94) from [<c07283e0>] (ret_from_exception+0x0/0x10) <4>[ 89.665728] Exception stack(0xdc02ffb0 to 0xdc02fff8) <4>[ 89.665758] ffa0: 00000001 40548448 00000000 4576c008 <4>[ 89.665789] ffc0: 00015a36 00052378 40548448 40548448 00000003 801a6610 80198a08 8018abbf <4>[ 89.665850] ffe0: 801a6828 beb0c340 80151525 8016d202 00000030 ffffffff <3>[ 94.671801] set_dload_mode <0> ( c0171bf8 ) <5>[ 94.671862] Going down for restart now On Fri, Sep 2, 2011 at 12:56 PM, Mulyadi Santosa <mulyadi.santosa@gmail.com>wrote:
Hi :)
On Fri, Sep 2, 2011 at 13:03, sandeep kumar <coolsandyforyou@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 init process something is causing kernel panic. .....[cut].... [<c01039d8>] (do_signal+0x68/0x640) <4>[ 85.237359] [<c01039d8>] (do_signal+0x68/0x640) from [<c0103fc8>] (do_notify_resume+0x18/0x38) <4>[ 85.237450] [<c0103fc8>] (do_notify_resume+0x18/0x38) from [<c0100bd0>] (work_pending+0x1c/0x20)
with the asumption that Android kernel is just another version of Linux kernel, I think this backtrace shows us that something is wrong with one (or more) work queue (or thread worker? something like that) you or somebody else has made.
So, do you recally creating one?
<0>[ 85.237542] Rebooting in 5 seconds.. <2>[ 85.237572] CPU0: stopping <4>[ 85.237603] [<c01076b8>] (unwind_backtrace+0x0/0x164) from [<c0100338>] (do_IPI+0xd8/0x154) <4>[ 85.237695] [<c0100338>] (do_IPI+0xd8/0x154) from [<c0728188>] (__irq_usr+0x48/0xe0)
So, rebooting fails? looks like something is clobbering the kernel stack way too much IMHO...
<4>[ 85.237756] Exception stack(0xdc18dfb0 to 0xdc18dff8) <4>[ 85.237817] dfa0: 00000000 0000007c 00000000 4097b240 <4>[ 85.237878] dfc0: 45957cfe 4ba95bd8 4fc24a48 000000f4 80118200 ffffe9f4 00000000 801a6374 <4>[ 85.237939] dfe0: 000000f4 4fc249f8 8011d0a8 8011bf18 20000010 ffffffff
I am not familiar with those register names, sorry...
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
-- With regards, Sandeep Kumar Anantapalli,