SAMA5D3 Kernel panic on boot: run-init: /sbin/init

[sector]

Dear all,

I have built the kernel for my sama5d3 xplained, but when I try to boot it, it hangs like you can see below:

Code: Select all

Freeing unused kernel memory: 152K (c06cb000 - c06f1000)
/sbin/init: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

CPU: 0 PID: 1 Comm: init Not tainted 3.10.0 #1
[<c0011ef0>] (unwind_backtrace+0x0/0xf4) from [<c001081c>] (show_stack+0x10/0x14)
[<c001081c>] (show_stack+0x10/0x14) from [<c0470c1c>] (panic+0x90/0x1d0)
[<c0470c1c>] (panic+0x90/0x1d0) from [<c001e764>] (do_exit+0x740/0x7f0)
[<c001e764>] (do_exit+0x740/0x7f0) from [<c001f3f0>] (do_group_exit+0x40/0x9c)
[<c001f3f0>] (do_group_exit+0x40/0x9c) from [<c001f45c>] (__wake_up_parent+0x0/0x18)

Do you know how to solve it?
Thank you very much

Regards

[blue_z]

How did you get into this situation?
What toolchain did you use to build the kernel (e.g. what libc does it use, hard or soft floating-point)?
What is the origin of the rootfs (i.e. did you build this rootfs with the same toolchain)? What libc is installed? Is /lib intact?

FWIW mixing-n-matching a kernel with an old rootfs is problematic.
And you're posting in the wrong forum (SAM7).

[sector]

I am following this outline: https://github.com/atwilc3000/driver/wi ... 3-xplained

It's true than when I use the rootfs file by default I can finish the flashing process successfully, but I haven't got the utilities that I marked during the kernel building process (like I marked in menuconfig). I don't know if it is due to I am not using the right rootfs (the one built together with the kernel). In this way, I tried to boot the kernel with the rootfs given by the kernel building process but I get the error showed up in the previous post.

I use the same toolchain to build the kernel and the rootfs, this: gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf
Related to the lib, I am using libc 2.17.
Maybe, is there an incompatibilty between the rootfs and the kernel?

Thank you.

Regards.

P.D: Sorry for not to post in the right forum (I am pretty new here).

[blue_z]

It's true than when I use the rootfs file by default I can finish the flashing process successfully, but I haven't got the utilities that I marked during the kernel building process (like I marked in menuconfig). I don't know if it is due to I am not using the right rootfs (the one built together with the kernel). In this way, I tried to boot the kernel with the rootfs given by the kernel building process but I get the error showed up in the previous post.

I don't understand what you wrote.
> ... if it is due to I am not using the right rootfs ...
Since your other posts indicate that you're using Yocto, I have no advice in that regard.

At this point the next thing I would do would be to inspect the /lib directory of the rootfs for the unopenable library.
If the rootfs isn't on removable media, then I'd boot a kernel with an initramfs or use NFS, and then mount that filesystem.

Regards