AnsweredAssumed Answered

i.mx6q hangs at Starting kernel log daemon...

Question asked by shijun zhao on Aug 24, 2017
Latest reply on Aug 31, 2017 by Joan Xie

The hardware is i.mx6q sabresd board. 

The rootfs I'm using is fsl-image-qt5-validation-imx-fb-imx6qdlsolo in L4.1.15_2.0.0-ga_images_MX6QDLSOLO, and I don't modify the rootfs.

The Linux version is imx_4.1.15_2.0.0_ga.

The rootfs is mounted through NFS.

 

When I boot the board, it hangs on Starting kernel log daemon... for a long time (about several minutes), and then it hands at umount: /mnt/.psplash: umount failed: No such file or directory. The print log is:

 

.........

/etc/network/if-pre-up.d/nfsroot: line 12: /proc/mounts: No such file or directory
run-parts: /etc/network/if-pre-up.d/nfsroot: exit status 1
Starting system message bus: Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": No such file or directory
dbus.
/etc/rc5.d/S05connman: line 15: /proc/mounts: No such file or directory
/etc/rc5.d/S10dropbear: line 32: /proc/mounts: No such file or directory
Starting Dropbear SSH server: dropbear.
Starting rpcbind daemon...done.
starting statd: done
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting atd: OK
exportfs: can't open /etc/exports for reading
grep: /proc/filesystems: No such file or directory
NFS daemon support not enabled in kernel
Starting system log daemon...0
Starting kernel log daemon...
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [fail]
Starting Telephony daemon
Starting Linux NFC daemon
Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Starting crond: OK
Running local boot scripts (/etc/rc.local)/etc/rc.local: line 15: /proc/sys/vm/min_free_kbytes: No such file or directory
error
umount: /mnt/.psplash: umount failed: No such file or directory

Outcomes