Location: http://autobuilder.yoctoproject.org/pub/nightly/20130226-2 branch: danny poky: 98292d1ef1cb44cf96f0a28fbca6439eda55ce1b meta-fsl-ppc: fa713448e2dfe12487e0d1ec4c610baa26cf2ef4 u-boot setting: ############### setenv bootcmd 'setenv bootargs root=/dev/sda5 rw console=$consoledev,$baudrate $othbootargs; sata init; ext2load sata 0:5 $loadaddr /boot/uImage; ext2load sata 0:5 $fdtaddr /boot/dtb_file; bootm $loadaddr - $fdtaddr' boot ############### The rootfs is deployed in the SATA disk. There are some error message in dmesg when system boot up. ############# root@p1022ds:/var/log# dmesg |grep error fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22 fsl-pq_mdio: probe of ffe25000.mdio failed with error -16 snd-soc-p1022ds: probe of snd-soc-p1022ds.0 failed with error -22 end_request: I/O error, dev nbd3, sector 2 EXT3-fs (nbd3): error: unable to read superblock end_request: I/O error, dev nbd8, sector 2 EXT3-fs (nbd8): error: unable to read superblock end_request: I/O error, dev nbd0, sector 2 EXT3-fs (nbd0): error: unable to read superblock end_request: I/O error, dev nbd10, sector 2 EXT3-fs (nbd10): error: unable to read superblock end_request: I/O error, dev nbd12, sector 2 EXT3-fs (nbd12): error: unable to read superblock end_request: I/O error, dev nbd5, sector 2 EXT3-fs (nbd5): error: unable to read superblock end_request: I/O error, dev nbd11, sector 2 EXT3-fs (nbd11): error: unable to read superblock end_request: I/O error, dev nbd9, sector 2 EXT3-fs (nbd9): error: unable to read superblock end_request: I/O error, dev nbd3, sector 2 EXT2-fs (nbd3): error: unable to read superblock end_request: I/O error, dev nbd6, sector 2 EXT3-fs (nbd6): error: unable to read superblock end_request: I/O error, dev nbd14, sector 2 EXT3-fs (nbd14): error: unable to read superblock end_request: I/O error, dev nbd2, sector 2 EXT3-fs (nbd2): error: unable to read superblock end_request: I/O error, dev nbd1, sector 2 EXT3-fs (nbd1): error: unable to read superblock end_request: I/O error, dev nbd13, sector 2 EXT3-fs (nbd13): error: unable to read superblock end_request: I/O error, dev nbd11, sector 2 EXT2-fs (nbd11): error: unable to read superblock end_request: I/O error, dev nbd4, sector 2 EXT3-fs (nbd4): error: unable to read superblock end_request: I/O error, dev nbd15, sector 2 EXT3-fs (nbd15): error: unable to read superblock end_request: I/O error, dev nbd5, sector 2 EXT2-fs (nbd5): error: unable to read superblock end_request: I/O error, dev nbd7, sector 2 EXT3-fs (nbd7): error: unable to read superblock end_request: I/O error, dev nbd8, sector 2 EXT2-fs (nbd8): error: unable to read superblock end_request: I/O error, dev nbd11, sector 0 end_request: I/O error, dev nbd10, sector 2 EXT2-fs (nbd10): error: unable to read superblock end_request: I/O error, dev nbd9, sector 2 EXT2-fs (nbd9): error: unable to read superblock end_request: I/O error, dev nbd6, sector 2 EXT2-fs (nbd6): error: unable to read superblock end_request: I/O error, dev nbd1, sector 2 EXT2-fs (nbd1): error: unable to read superblock end_request: I/O error, dev nbd2, sector 2 EXT2-fs (nbd2): error: unable to read superblock end_request: I/O error, dev nbd4, sector 2 EXT2-fs (nbd4): error: unable to read superblock end_request: I/O error, dev nbd12, sector 2 EXT2-fs (nbd12): error: unable to read superblock end_request: I/O error, dev nbd15, sector 2 EXT2-fs (nbd15): error: unable to read superblock end_request: I/O error, dev nbd14, sector 2 EXT2-fs (nbd14): error: unable to read superblock end_request: I/O error, dev nbd0, sector 2 EXT2-fs (nbd0): error: unable to read superblock end_request: I/O error, dev nbd3, sector 0 end_request: I/O error, dev nbd5, sector 0 end_request: I/O error, dev nbd13, sector 2 EXT2-fs (nbd13): error: unable to read superblock end_request: I/O error, dev nbd7, sector 2 EXT2-fs (nbd7): error: unable to read superblock end_request: I/O error, dev nbd8, sector 0 end_request: I/O error, dev nbd10, sector 0 end_request: I/O error, dev nbd9, sector 0 end_request: I/O error, dev nbd6, sector 0 end_request: I/O error, dev nbd1, sector 0 end_request: I/O error, dev nbd2, sector 0 end_request: I/O error, dev nbd4, sector 0 EXT3-fs (sda4): error: unable to read superblock end_request: I/O error, dev nbd12, sector 0 end_request: I/O error, dev nbd15, sector 0 end_request: I/O error, dev nbd14, sector 0 end_request: I/O error, dev nbd0, sector 0 end_request: I/O error, dev nbd13, sector 0 end_request: I/O error, dev nbd7, sector 0 EXT2-fs (sda4): error: unable to read superblock NTFS-fs error (device sda4): read_ntfs_boot_sector(): Primary boot sector is invalid. NTFS-fs error (device sda4): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. NTFS-fs error (device sda4): ntfs_fill_super(): Not an NTFS volume. root@p1022ds:/var/log# ##############
Created attachment 1089 [details] full dmesg log I attached the full message log.
(In reply to comment #1) > Created attachment 1089 [details] > full dmesg log > > I attached the full message log. This occurs when trying to automount file systems. Not sure of the best fix yet.
Besides the filesystem-related error messages, there are some other errors: Feb 28 08:03:49 p1022ds user.warn kernel: fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22 Feb 28 08:03:49 p1022ds user.warn kernel: fsl-pq_mdio: probe of ffe25000.mdio failed with error -16 Feb 28 08:03:49 p1022ds user.warn kernel: snd-soc-p1022ds: probe of snd-soc-p1022ds.0 failed with error -22
1. fix "fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22" please set 'othbootargs ' in uboot. u-boot setting: ####################### setenv othbootargs cache-sram=0xfff00000,0x8000 ####################### 2. fix "snd-soc-p1022ds: probe of snd-soc-p1022ds.0 failed with error -22" please set 'hwconfig' in uboot. u-boot setting: ####################### setenv hwconfig audclk:12 ####################### 3. fix "EXT3-fs (nbd3): error: unable to read superblock" please disable the option Network block device support in kernel. The option can be found in menuconfig under Device Drivers-> Block devices- >Network block device support options . 4. "fsl-pq_mdio: probe of ffe25000.mdio failed with error -16" fsl-pq_mdio can config for two PHY . there is only PHY in some p1022ds boards. so ,there are errors sometime. I tested successfully in p1022ds board by those ways.
set 'othbootargs ' and 'hwconfig' in uboot.
*** Bug 3451 has been marked as a duplicate of this bug. ***