NFS boot fails

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NFS boot fails

428 Views
Josh-256
Contributor I

Hi All

I have 2 different imx boards. One, a module and another an SBC - Avnet Maax board. Both of them are based on the same processor. I would like to work on both with TFTP and NFS rootfs. My rootfs is based on Yocto and have used the rootfs from the module.

I would like to use the same rootfs for both the devices but different kernel and dtb files in the tftp

The module seems to boot and work correctly. But when I try to boot the SBC on the same nfs (different kernel and dtb), the nfs seems to be mounted, but the init fails, and I get a crash as shown below. 

My boot argument 

setenv bootargs console=${console} root=/dev/nfs rw nfsroot=${serverip}:/nfs,nfsvers=4,tcp ip=${ipaddr}::${serverip}:::eth0:off

I have the detailed log from the error below, which shows that nfs file system has been mounted.

Could anyone please point me to the mistake?

Regards

Prajosh Premdas

 

[ 5.005855] VFS: Mounted root (nfs filesystem) on device 0:21.
[ 5.014968] devtmpfs: mounted
[ 5.019189] Freeing unused kernel memory: 2944K
[ 5.036834] Run /sbin/init as init process
[ 5.742715] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[ 5.750385] CPU: 1 PID: 1 Comm: init Not tainted 5.4.24-2.1.0+ge4abce0bad07 #1
[ 5.757605] Hardware name: Avnet Maaxboard (DT)
[ 5.762133] Call trace:
[ 5.764586] dump_backtrace+0x0/0x140
[ 5.768248] show_stack+0x14/0x20
[ 5.771564] dump_stack+0xb4/0xf8
[ 5.774879] panic+0x158/0x324
[ 5.777934] do_exit+0x950/0x980
[ 5.781161] do_group_exit+0x40/0xa0
[ 5.784737] get_signal+0xd0/0x688
[ 5.788139] do_notify_resume+0x1fc/0x460
[ 5.792147] work_pending+0x8/0x10
[ 5.795551] SMP: stopping secondary CPUs
[ 5.799989] Kernel Offset: disabled
[ 5.803476] CPU features: 0x0002,2000200c
[ 5.807482] Memory Limit: none

0 Kudos
3 Replies

413 Views
joanxie
NXP TechSupport
NXP TechSupport

what processor and yocto bsp do you use?

0 Kudos

406 Views
Josh-256
Contributor I

Hi

The processor I am using  NXP i.MX 8M Nano -  i.MX8MQ rev2.1 1500 MHz

I am using Yoctos zeus version

Regards

Prajosh 

0 Kudos

390 Views
joanxie
NXP TechSupport
NXP TechSupport

normally this issue is caused by the memory conflict, so you need check your memory settings

0 Kudos