i.MX ProcessorsのトピックNFS boot fails https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1675812#M208127 <P>Hi All</P><P>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.</P><P>I would like to use the same rootfs for both the devices but different kernel and dtb files in the tftp</P><P>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.&nbsp;</P><P><STRONG>My boot argument&nbsp;</STRONG></P><P><STRONG>setenv bootargs console=${console} root=/dev/nfs rw nfsroot=${serverip}:/nfs,nfsvers=4,tcp ip=${ipaddr}::${serverip}:::eth0:off</STRONG></P><P>I have the detailed log from the error below, which shows that nfs file system has been mounted.</P><P>Could anyone please point me to the mistake?</P><P>Regards</P><P>Prajosh Premdas</P><P>&nbsp;</P><P>[ 5.005855] VFS: Mounted root (nfs filesystem) on device 0:21.<BR />[ 5.014968] devtmpfs: mounted<BR />[ 5.019189] Freeing unused kernel memory: 2944K<BR />[ 5.036834] Run /sbin/init as init process<BR />[ 5.742715] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004<BR />[ 5.750385] CPU: 1 PID: 1 Comm: init Not tainted 5.4.24-2.1.0+ge4abce0bad07 #1<BR />[ 5.757605] Hardware name: Avnet Maaxboard (DT)<BR />[ 5.762133] Call trace:<BR />[ 5.764586] dump_backtrace+0x0/0x140<BR />[ 5.768248] show_stack+0x14/0x20<BR />[ 5.771564] dump_stack+0xb4/0xf8<BR />[ 5.774879] panic+0x158/0x324<BR />[ 5.777934] do_exit+0x950/0x980<BR />[ 5.781161] do_group_exit+0x40/0xa0<BR />[ 5.784737] get_signal+0xd0/0x688<BR />[ 5.788139] do_notify_resume+0x1fc/0x460<BR />[ 5.792147] work_pending+0x8/0x10<BR />[ 5.795551] SMP: stopping secondary CPUs<BR />[ 5.799989] Kernel Offset: disabled<BR />[ 5.803476] CPU features: 0x0002,2000200c<BR />[ 5.807482] Memory Limit: none</P> Mon, 26 Jun 2023 08:18:34 GMT Josh-256 2023-06-26T08:18:34Z NFS boot fails https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1675812#M208127 <P>Hi All</P><P>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.</P><P>I would like to use the same rootfs for both the devices but different kernel and dtb files in the tftp</P><P>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.&nbsp;</P><P><STRONG>My boot argument&nbsp;</STRONG></P><P><STRONG>setenv bootargs console=${console} root=/dev/nfs rw nfsroot=${serverip}:/nfs,nfsvers=4,tcp ip=${ipaddr}::${serverip}:::eth0:off</STRONG></P><P>I have the detailed log from the error below, which shows that nfs file system has been mounted.</P><P>Could anyone please point me to the mistake?</P><P>Regards</P><P>Prajosh Premdas</P><P>&nbsp;</P><P>[ 5.005855] VFS: Mounted root (nfs filesystem) on device 0:21.<BR />[ 5.014968] devtmpfs: mounted<BR />[ 5.019189] Freeing unused kernel memory: 2944K<BR />[ 5.036834] Run /sbin/init as init process<BR />[ 5.742715] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004<BR />[ 5.750385] CPU: 1 PID: 1 Comm: init Not tainted 5.4.24-2.1.0+ge4abce0bad07 #1<BR />[ 5.757605] Hardware name: Avnet Maaxboard (DT)<BR />[ 5.762133] Call trace:<BR />[ 5.764586] dump_backtrace+0x0/0x140<BR />[ 5.768248] show_stack+0x14/0x20<BR />[ 5.771564] dump_stack+0xb4/0xf8<BR />[ 5.774879] panic+0x158/0x324<BR />[ 5.777934] do_exit+0x950/0x980<BR />[ 5.781161] do_group_exit+0x40/0xa0<BR />[ 5.784737] get_signal+0xd0/0x688<BR />[ 5.788139] do_notify_resume+0x1fc/0x460<BR />[ 5.792147] work_pending+0x8/0x10<BR />[ 5.795551] SMP: stopping secondary CPUs<BR />[ 5.799989] Kernel Offset: disabled<BR />[ 5.803476] CPU features: 0x0002,2000200c<BR />[ 5.807482] Memory Limit: none</P> Mon, 26 Jun 2023 08:18:34 GMT https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1675812#M208127 Josh-256 2023-06-26T08:18:34Z Re: NFS boot fails https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1675933#M208142 <P>what processor and yocto bsp do you use?</P> Mon, 26 Jun 2023 10:05:04 GMT https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1675933#M208142 joanxie 2023-06-26T10:05:04Z Re: NFS boot fails https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1676007#M208148 <P>Hi</P><P>The processor I am using&nbsp; NXP i.MX 8M Nano -&nbsp;&nbsp;i.MX8MQ rev2.1 1500 MHz</P><P>I am using Yoctos zeus version</P><P>Regards</P><P>Prajosh&nbsp;</P> Mon, 26 Jun 2023 11:48:34 GMT https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1676007#M208148 Josh-256 2023-06-26T11:48:34Z Re: NFS boot fails https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1678350#M208323 <P>normally this issue is caused by the memory conflict, so you need check your memory settings</P> Thu, 29 Jun 2023 05:30:05 GMT https://community.nxp.com/t5/i-MX-Processors/NFS-boot-fails/m-p/1678350#M208323 joanxie 2023-06-29T05:30:05Z