Hi!
I have a Beagleboard clone with connected KSZ8851SNL for the network feature. Succesfully ported Android ICS starts and I can see watches and the application button. However soon the system goes to panic and I think it is connected with the KSZ8851 because I see a lot of complains:
init: no such service 'dhcpcd_eth0'
init: no such service 'dhcpcd_eth0'
init: no such service 'dhcpcd_eth0:-h android-b4fde85cb1e6c847 eth0'
init: untracked pid 1161 exited
binder: release 1240:1240 transaction 7753 out, still active
init: untracked pid 1240 exited
init: untracked pid 1254 exited
binder: release 1273:1273 transaction 7721 out, still active
init: untracked pid 1176 exited
init: untracked pid 1273 exited
init: untracked pid 1289 exited
alarm_release: clear alarm, pending 0
alarm_release: clear alarm, pending 0
init: untracked pid 1316 exited
binder: release 1176:1176 transaction 7944 in, still active
binder: send failed reply for transaction 7944 to 1254:1254
binder: release 1176:1187 transaction 7809 in, still active
binder: send failed reply for transaction 7809 to 1316:1316
binder: release 1176:1188 transaction 7753 in, still active
binder: send failed reply for transaction 7753, target dead
binder: release 1176:1320 transaction 7722 out, still active
binder: release 1176:1320 transaction 7721 in, still active
binder: release 1176:1351 transaction 7945 in, still active
binder: send failed reply for transaction 7945 to 1316:1353
binder: release 1176:1354 transaction 7886 in, still active
binder: send failed reply for transaction 7886 to 1289:1289
init: untracked pid 1332 exited
binder: release 1082:1082 transaction 7184 in, still active
binder: send failed reply for transaction 7184 to 1090:1093
binder: release 1082:1294 transaction 7722 in, still active
binder: send failed reply for transaction 7722, target dead
binder: send failed reply for transaction 7721, target dead
binder: release 1363:1363 transaction 8197 in, still active
binder: send failed reply for transaction 8197 to 1371:1373
init: untracked pid 1362 exited
request_suspend_state: wakeup (0->0) at 108915557863 (2012-12-13 13:42:17.287994385 UTC)
init: no such service 'dhcpcd_eth0'
init: no such service 'dhcpcd_eth0'
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c004965c>] (dump_backtrace+0x0/0x110) from [<c04b4a6c>] (dump_stack+0x18/0x1c)
r7:cf019dc0 r6:cf015ac0 r5:c066e528 r4:c066e528
[<c04b4a54>] (dump_stack+0x0/0x1c) from [<c04b4ad4>] (panic+0x64/0x180)
[<c04b4a70>] (panic+0x0/0x180) from [<c0073ac0>] (do_exit+0x7c/0x638)
r3:c0635ad0 r2:cf015bf0 r1:00000000 r0:c059d5f0
[<c0073a44>] (do_exit+0x0/0x638) from [<c0074100>] (do_group_exit+0x84/0xb4)
[<c007407c>] (do_group_exit+0x0/0xb4) from [<c0081224>] (get_signal_to_deliver+0x344/0x380)
r5:cf01bec8 r4:00106001
[<c0080ee0>] (get_signal_to_deliver+0x0/0x380) from [<c00482d4>] (do_signal+0x70/0x660)
[<c0048264>] (do_signal+0x0/0x660) from [<c00488e4>] (do_notify_resume+0x20/0x64)
[<c00488c4>] (do_notify_resume+0x0/0x64) from [<c0045118>] (work_pending+0x24/0x28)
I just inserted the same KSZ881 initialization from a Linux kernel and probably it requires also some magic steps to enable KSZ8851 in the 2.6.37 based Android kernel. Please assist if your know