UbiFS + HWECC(?) + BeagleBoard = fail
Hi. After moving to upstream 2.6.3{5,6,7} kernels, i forced to use jffs2 instead of ubifs, because of lot CRC errors. If i use prefetch/dma, i can attach to ubi, make volume, write data, reboot - and got lots of CRC errors. Without prefetch i just couldn't do anything to ubi. Looks like hw/sw bug in ubi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[no subject]
subscribe linux-omap -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
UbiFS regression(?)
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 0:0, read 64 bytes UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 0:1, read 64 bytes . root=ubi0:rootfs rw rootwait ubi.mtd=4 rootfstype=ubifs beagleboard 2.6.35-beagle-32op-08909-g8428498 last commit: 842849896627701e4c07441f2c7519aeec771058 CONFIG_MTD_UBI=y CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_RESERVE=1 CONFIG_UBIFS_FS=y CONFIG_UBIFS_FS_XATTR=y CONFIG_UBIFS_FS_ADVANCED_COMPR=y CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html