information posted is not so detailed, please add print to the init program and find where is the exact point that cased this panic
On 12月9日, 下午5时34分, Kolanchinathan S <kolanch...@gmail.com> wrote: > Hi All, > > I am porting the android kernel in DM365. while booting I am > facing problem like Kernel panic - not syncing: Attempted to kill > init!, I mentioned the error log message in below. > > My Android kernel version 2.6.32 > > Gingerbread Root File System(2.3) > > My bootargs > > setenv bootargs console=ttyS0,115200n8 init=/init ip=dhcp rw root=/dev/ > nfs nfsroot=$(nfshost)(rootpath),nolock > rootwait mem=120M androidboot.console=ttyS0 dm365_imp.oper_mode=0 > davincihd_capture.channel0_numbuffers=4 > > Log message > > Looking up port of RPC 100003/2 on 10.1.3.247 > Looking up port of RPC 100005/1 on 10.1.3.247 > VFS: Mounted root (nfs filesystem) on device 0:13. > Freeing init memory: 120K > Warning: unable to open an initial console. > Kernel panic - not syncing: Attempted to kill init! > Backtrace: > [<c002a984>] (dump_backtrace+0x0/0x114) from [<c0240374>] (dump_stack > +0x18/0x1c) > r7:c7025ee0 r6:c7020000 r5:c7020000 r4:c030be78 > [<c024035c>] (dump_stack+0x0/0x1c) from [<c02403cc>] (panic > +0x54/0x12c) > [<c0240378>] (panic+0x0/0x12c) from [<c003ff80>] (do_exit+0x74/0x654) > r3:c02f8b60 r2:c7024000 r1:c7025e58 r0:c02b0dd1 > [<c003ff0c>] (do_exit+0x0/0x654) from [<c0040620>] (do_group_exit > +0xc0/0xf0) > [<c0040560>] (do_group_exit+0x0/0xf0) from [<c004c644>] > (get_signal_to_deliver+0x3a4/0x404) > r7:c7025ee0 r6:c7025fb0 r5:c7024000 r4:0000000b > [<c004c2a0>] (get_signal_to_deliver+0x0/0x404) from [<c00295e8>] > (do_notify_resume+0x64/0x680) > [<c0029584>] (do_notify_resume+0x0/0x680) from [<c0026fa8>] > (work_pending+0x1c/0x20) -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
