On Sat, Feb 27, 2016 at 10:23 AM, Matt Madison <[email protected]> wrote: > On Sat, Feb 27, 2016 at 4:12 AM, Otavio Salvador > <[email protected]> wrote: >> On Sat, Feb 27, 2016 at 9:03 AM, Fabio Estevam <[email protected]> wrote: > [...] >>> However in the second boot it failed to found the rootfs, which seems >>> to match what Matt reported: > [...] >>> All subsequent boots failed as well. >> >> I think I know what is going on; instead of plugging out the power >> cable, issue a reboot in the first time. It will work afterwards it >> seems. > > The problem I was reporting was U-Boot being unable to read the ext4 > rootfs properly (using ext4ls, for instance). Linux had no problem > with it. > > And it looks like the problem is that U-Boot's ext4 filesystem support > doesn't understand some of the more recent features that have been > added. In particular, I found that by adding > > EXTRA_IMAGECMD_append_ext4 = " -O ^flex_bg" > > to my image recipe, to disable that particular ext4 feature, clears up > the problem I was seeing on my Wandboard, at least with jethro builds. > That seems to be enough, at least - I couldn't really tell from > reading the U-Boot ext4 code which features it really does support. > > This doesn't affect the default SDcard images that much, since the > kernel and device tree get put into a FAT partition anyway, so U-Boot > doesn't have to read the rootfs partition. It was more of a problem > for my custom board, because there I don't use the default layout, and > instead bundle the kernel and device tree with the rootfs. > > With builds off master, the newer e2fsprogs from OE-Core master also > defaults to enabling the metadata_csum feature, and mke2fs issues a > warning about moving to a 3.18 or later kernel during the filesystem > creation (when run directly on my board with the 3.14-based kernel), > due to instability of that feature in older kernels. So we could see > some other issues crop up going forward, too.
Great! EXTRA_IMAGECMD_append_ext4 = " -O ^flex_bg -O ^metadata_csum" Is worth test Fabio, it might solve the error you were seeing in the first boot when plugging the power cable or doing a dirty reset. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
