ARM GCC-4.2.1 dynamically linked busybox-1.15.0 failed

Teh Kok How khteh at smartbridges.com
Tue Sep 15 04:00:38 UTC 2009


Hi;
	I am using snapgear arm-linux-tools-20070808 with gcc-4.2.1 to build
busybox-1.15.0. Building busybox as statically linked binary is fine.
However, I have never been able to use the dynamically linked busybox
binary. It can't even get to the first C-code of init/init.c. Here is the
failed busybox console log:

<snip>
IP-Config: Complete:
     device=eth0, addr=10.0.51.200, mask=255.255.255.0, gw=255.255.255.255,
     host=ixdp425, domain=, nis-domain=(none),
     bootserver=10.0.51.16, rootserver=10.0.51.16, rootpath=
Looking up port of RPC 100003/2 on 10.0.51.16
Looking up port of RPC 100005/1 on 10.0.51.16
VFS: Mounted root (nfs filesystem) on device 0:13.
Freeing init memory: 108K
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0027790>] (dump_backtrace+0x0/0x110) from [<c0027c54>]
(dump_stack+0x18/0x1c)
 r6:c03ad948 r5:c03c9f84 r4:c03ad948
[<c0027c3c>] (dump_stack+0x0/0x1c) from [<c0044cd8>] (panic+0x54/0x13c)
[<c0044c84>] (panic+0x0/0x13c) from [<c0048530>] (do_exit+0x64/0x684)
 r3:00000000 r2:c381a000 r1:00000000 r0:c035bcb0
[<c00484cc>] (do_exit+0x0/0x684) from [<c0048c08>] (do_group_exit+0xb8/0xec)
[<c0048b50>] (do_group_exit+0x0/0xec) from [<c005325c>]
(get_signal_to_deliver+0x39c/0x3f4)
 r6:c381a000 r5:0000000b r4:000000dc
[<c0052ec0>] (get_signal_to_deliver+0x0/0x3f4) from [<c0026170>]
(do_signal+0x64/0x53c)
[<c002610c>] (do_signal+0x0/0x53c) from [<c0026674>]
(do_notify_resume+0x2c/0x30)
[<c0026648>] (do_notify_resume+0x0/0x30) from [<c0023e6c>]
(work_pending+0x1c/0x20)
Rebooting in 1 seconds..

	Any insight and advice is appreciated. Thanks.

Regards,
Teh



More information about the busybox mailing list