Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130131-4/machines/p1022ds/ poky: "1.4_M3:3ae1a4ba972cfc17ff3f2fda632da8ecc3414885" meta-fsl-ppc: "1.4_M3:ee364575803812dbbb2b103d468c66c54efcc7af" When booting up via nfs, the system would print the following message, then no response anymore. #################### ... ... Registering the dns_resolver key type drivers/rtc/hctosys.c: unable to open rtc device (rtc0) ADDRCONF(NETDEV_UP): eth0: link is not ready PHY: mdio@ffe24000:01 - Link is Up - 100/Full ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready IP-Config: Complete: device=eth0, addr=128.224.162.252, mask=255.255.254.0, gw=128.224.162.1, host=p1022ds, domain=, nis-domain=(none), bootserver=128.224.162.200, rootserver=128.224.162.200, rootpath= VFS: Mounted root (nfs filesystem) on device 0:15. Freeing unused kernel memory: 268k freed INIT: version 2.88 booting Starting udev Starting Bootlog daemon: bootlogd: cannot find console device 4:64 under /dev bootlogd. Configuring network interfaces... ifup skipped for nfsroot interface eth0 run-parts: /etc/network/if-pre-up.d/nfsroot exited with code 1 Starting rpcbind daemon...rpcbind: fork failed: No such device done. hwclock: can't open '/dev/misc/rtc': No such file or directory Thu Jan 31 19:01:00 UTC 2013 hwclock: can't open '/dev/misc/rtc': No such fil #################### Uboot settings: ################## setenv ipaddr 128.224.162.252 setenv serverip 128.224.162.200 setenv gatewayip 128.224.162.1 setenv netmask 255.255.254.0 tftp 1000000 uImage tftp c00000 p1022ds.dtb bootm 1000000 - c00000 setenv bootargs root=/dev/nfs rw nfsroot=128.224.162.200:/export/pxeboot/rootfs ip=128.224.162.252:128.224.162.200:128.224.162.1:255.255.254.0:p1022ds:eth0:off console=ttyS0,115200 ##################
Created attachment 1056 [details] The full boot log
The system also can not boot up via sata disk: ############## INIT: version 2.88 booting Starting udev Starting Bootlog daemon: bootlogd: cannot find console device 4:64 under /dev bootlogd. Configuring network interfaces... ADDRCONF(NETDEV_UP): eth0: link is not ready udhcpc (v1.20.2) started Sending discover... PHY: mdio@ffe24000:01 - Link is Up - 100/Full ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Sending discover... Sending select for 128.224.162.146... Lease of 128.224.162.146 obtained, lease time 172800 /etc/udhcpc.d/50default: Adding DNS 128.224.160.11 /etc/udhcpc.d/50default: Adding DNS 147.11.57.128 /etc/udhcpc.d/50default: Adding DNS 147.11.57.133 done. Starting rpcbind daemon...rpcbind: fork failed: No such device done. hwclock: can't open '/dev/misc/rtc': No such file or directory Thu Jan 31 19:01:00 UTC 2013 hwclock: can't open '/dev/misc/reth0: no IPv6 routers present ###############
This issue still happens in 20130213 build. git rev: meta-yocto = "master:3ec4df57540421df2cda6b83c615bfb7cebccefd" meta-fsl-ppc = "master:877cb8b1374c59737ffbe6f33e031b571284c8f9" Maybe this issue is caused by udev. When I remove the udev start script in /etc/rc5.d/ , the system can login. ############### root@p1022ds:~# root@p1022ds:~# ps | grep udev 1547 root 2600 S grep udev root@p1022ds:~# ls /dev apm_bios hda13 hda3 kmem mtd3 mtdblock3 ram0 tty2 ttySA0 console hda14 hda4 kmsg mtd4 mtdblock4 ram1 tty3 urandom fb0 hda15 hda5 log mtd5 mtdblock5 ram2 tty4 zero hda hda16 hda6 mem mtd6 mtdblock6 ram3 tty5 hda1 hda17 hda7 mtab mtd7 mtdblock7 random tty6 hda10 hda18 hda8 mtd0 mtdblock0 null tty tty7 hda11 hda19 hda9 mtd1 mtdblock1 ptmx tty0 tty8 hda12 hda2 initctl mtd2 mtdblock2 pts tty1 ttyS0 root@p1022ds:~# root@p1022ds:~# ############### If I start the udev manually, seems it can not create dev file correctly in /dev/ : ############### root@p1022ds:~# /etc/init.d/udev start Starting udev root@p1022ds:~# root@p1022ds:~# ps | grep udev 1560 root 3508 S /lib/udev/udevd -d 1779 root 3504 S /lib/udev/udevd -d 1835 root 3504 S /lib/udev/udevd -d 2257 root 2600 S grep udev root@p1022ds:~# root@p1022ds:~# ls /dev/ core initctl null shm stdin udev_network_queue fd kmsg pts stderr stdout root@p1022ds:~# ##############
Would someone can take a look at this bug ? It blocks the testing on on recent builds.
please apply 94a58c153958002b117fcb5eeaef3d22be71a0f6 of poky, make sure rpm is built into rootfs and try again. seems the run-postinsts is missing from rootfs by default.
this issue is caused by udev. udev182 needs CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT in kernel. please enable the option Automount devtmpfs at /dev, after the kernel mounted the rootfs (CONFIG_DEVTMPFS_MOUNT) in kernel. The option can be found in menuconfig under Device Drivers-> Generic Driver options and is called Maintain a devtmpfs filesystem to mount at /dev. I tested successfully in p1022ds board by the way.
(In reply to comment #6) > this issue is caused by udev. > > udev182 needs CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT in kernel. > > please enable the option Automount devtmpfs at /dev, after the kernel > mounted the rootfs (CONFIG_DEVTMPFS_MOUNT) in kernel. > The option can be found in menuconfig under Device Drivers-> Generic Driver > options and is called Maintain a devtmpfs filesystem to mount at /dev. > > I tested successfully in p1022ds board by the way. (In reply to comment #6) > this issue is caused by udev. > > udev182 needs CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT in kernel. > > please enable the option Automount devtmpfs at /dev, after the kernel > mounted the rootfs (CONFIG_DEVTMPFS_MOUNT) in kernel. > The option can be found in menuconfig under Device Drivers-> Generic Driver > options and is called Maintain a devtmpfs filesystem to mount at /dev. > > I tested successfully in p1022ds board by the way. Could you please commit a patch for this ? Usually, QAs get the images from official autobuilder (for exapmle: http://autobuilder.yoctoproject.org/pub/nightly/20130325-1/machines/p1022ds/ ). We don't need to build the image in local. It is better to enable these configures by default. Then we can get the correct image from autobuilder and test it directly. Thanks, Yi
the patch for this applied in both dylan and master. meta-fsl-ppc = "master:5834aa107616f014952b282593fba563a70d2453" The udev is upgraded to 182, the /dev mount requires CONFIG_DEVTMPFS_MOUNT is enabled in Kernel, so enable the option for QorIQ SDK targets *** This bug has been marked as a duplicate of bug 3452 ***