0
votes

I'm using the buildroot version-20011.02 for kernel, toolchain and filesystem.My customized board ARMV7 cortexA9 SoC.Kernel version is 3.18.41. Build the kernel(uImage), Buildroot toolchain, rootfs.tar.gz. Enable the filesystem tyep ext4 in buildroot and also in kernel. Extracting this rootfs.tar.gz to /export/users/buildroot/. exporting this directory by using
exportfs -a, exportfs -rv and restart the nfs server.It seems everything is fine on nfs server side.
Here I'm sharing the "make menuconfig" system configuration -->

Init system (BusyBox)  --->

Even I tried with Init system (systemV) --->
with bootargs as bootargs console=ttyAM0,115200n8 root=/dev/nfs rw rootwait ip=dhcp nfsroot=192.168.1.40:/export/users/buildroot,tcp,v3 init=/sbin/init
Every time I'm getting below log:

VFS: mounted fs via nfs  
devtmpfs is mounted.  
Kernel panic - not syncing:Attempted to kill init, exit code=0x000000b 

Please help me out how to resolve this issue.

1
Try to isolate your problem. What if you build another kernel version? I suppose that you've read kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt that. - Alex Bender
Is that the entire stack in the log? If there is more it could be useful. - kabanus
What is /sbin/init? Is it softlink to systemd or just script? - user2699113
@AlexBender, I didn't try with another kernel version since made the changes in board file and other source files to customize this into our SoC.I want to stick with this kernel to resolve this issue.if you are suggesting i will give a try with another kernel.Do you think is it a problem with kernel? Yes I've read link you shared, its seems kernel command line i.e bootargs is proper thats why its mounting to nfs server from the log. Still if you are feeling I'm missing something in bootargs please feel free to comment. - shaikh kamal
@kabanus, I agree it would be more useful if i will share complete log, but sorry I'm working in so much secure environment. What I remember here I'm sharing. VFS: mounted fs via nfs devtmpfs is mounted. Freeing unused kenel memory... Kernel panic - not syncing:Attempted to kill init, exit code=0x000000b, Its seem kernel is trying to find that init , but not able find. I'm assuming.We need to debug this way what could be problem kernel can find this init after mounting nfs filesystem. - shaikh kamal

1 Answers

0
votes

This may help you.

As you said, there is a log like below.

Kernel panic - not syncing:Attempted to kill init, exit code=0x000000b 

This means init(busybox) is exited and the exit code is 0xb. So kernel goes into panic. Maybe this is caused by a network problem. But we cannot conclude this is due to network or not, for now.

You said, you saw crashing, without NFS. I think resolving that crash maybe better way to solve this situation.

Please share crash log without NFS configuration. If you share log, I will check it.