AnsweredAssumed Answered

IMX6UL platform. The same firmware image, different cpu version, the NFS mount unstable issue in the boot.

Question asked by Eric Chang on Jan 8, 2018
Latest reply on Jan 17, 2018 by Eric Chang

We use the same firmware image download to different CPU devices.

The old CPU version device can mount NFS in the boot. (CPU version v1.1)

But the new CPU version device can't  mount NFS in the boot. (CPU version v1.2)

 

CPU : IMX6UL version v1.1

           IMX6UL version v1.2

 

Kernel : 3.14.38

Platform : imx6ulevk

 

Attached files :      normal_nfs.log - CPU v1.1 boot log.(The image can mount NFS rootfs.)

                        no_normal_nfs.log - CPU v1.2 boot log.(The image can't mount NFS rootfs)

 

CPU v1.1 mount NFS log

----------------------------

IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: 2188000.ethernet:02 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, hwaddr=00:11:22:03:44:55, ipaddr=192.168.168.109, mask=255.255.255.0, gw=255.255.255.255
host=192.168.168.109, domain=, nis-domain=(none)
bootserver=255.255.255.255, rootserver=192.168.168.96, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing unused kernel memory: 332K (80817000 - 8086a000)
INIT: version 2.88 booting

Please wait: booting...
Starting udev
udevd[147]: starting version 182
random: nonblocking pool is initialized
bootlogd: cannot allocate pseudo tty: No such file or directory
INIT: Entering runlevel: 5

----------------------------

==> Success mount NFS rootfs

 

CPU v1.2 mount NFS log

----------------------------

Pv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: 2188000.ethernet:02 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, hwaddr=78:20:79:00:01:63, ipaddr=192.168.168.109, mask=255.255.255.0, gw=255.255.255.255
host=192.168.168.109, domain=, nis-domain=(none)
bootserver=255.255.255.255, rootserver=192.168.168.96, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing unused kernel memory: 332K (80817000 - 8086a000)
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
fec 2188000.ethernet eth0: rcv is not +last
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
nfs: server 192.168.168.96 OK
random: nonblocking pool is initialized
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 OK
nfs: server 192.168.168.96 OK
fec 2188000.ethernet eth0: rcv is not +last
nfs: server 192.168.168.96 not responding, still trying
nfs: server 192.168.168.96 not responding, still trying

......

---------------------------------

==> Don't success mount NFS rootfs.

 

Does anyone encounter the same problem?

 

Best Wishes,

Eric Chang

Outcomes