From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pa0-f42.google.com ([209.85.220.42]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1Tzecx-0004Jr-M9 for linux-mtd@lists.infradead.org; Mon, 28 Jan 2013 02:39:20 +0000 Received: by mail-pa0-f42.google.com with SMTP id rl6so1233711pac.1 for ; Sun, 27 Jan 2013 18:39:17 -0800 (PST) Message-ID: <5105E4CE.1090800@gmail.com> Date: Mon, 28 Jan 2013 08:09:10 +0530 From: Vikram Narayanan MIME-Version: 1.0 To: Huang Shijie Subject: Re: mtd_oobtest fails with GPMI-NAND References: <50F97DB5.7040801@gmail.com> <50FCA426.6030309@freescale.com> In-Reply-To: <50FCA426.6030309@freescale.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello Huang, On 1/21/2013 7:42 AM, Huang Shijie wrote: > 于 2013年01月19日 00:52, Vikram Narayanan 写道: >> Hi, >> >> When I try to run the mtd_oobtest on an i.Mx6Q board, it results in a >> failure with the following error. >> I'm using 3.5.7 Kernel. >> >> root@freescale:/# insmod mtd_oobtest.ko dev=6 >> [ 7534.508880] >> [ 7534.511228] ================================================= >> [ 7534.518460] mtd_oobtest: MTD device: 6 >> [ 7534.523000] mtd_oobtest: MTD device size 304087040, eraseblock size >> 262144, page size 4096, count of eraseblocks 1160, pages per >> eraseblock 64, OOB size 128 >> [ 7534.539301] mtd_oobtest: scanning for bad eraseblocks >> [ 7534.545345] mtd_oobtest: scanned 1160 eraseblocks, 0 are bad >> [ 7534.552482] mtd_oobtest: test 1 of 5 >> [ 7534.556797] mtd_oobtest: erasing whole device >> [ 7537.523540] mtd_oobtest: erased 1160 eraseblocks >> [ 7537.528888] mtd_oobtest: writing OOBs of whole device >> [ 7537.534704] mtd_oobtest: error: writeoob failed at 0x0 >> [ 7537.540562] mtd_oobtest: error: use_len 0, use_offset 0 >> [ 7537.546565] mtd_oobtest: error -22 occurred >> [ 7537.551456] ================================================= >> >> This boils down to the fake "struct nand_ecclayout" defined in >> >> >> Is there a way to run this test successfully? > The gpmi-nand may use all the oob. So the oobtest may fails. I'm in receipt of the error mentioned in [1]. The FAQ also suggests to run mtd_tests. mtd_oobtest might give more information on whether or not the NAND driver is buggy. Since I couldn't run this test on gpmi-nand due to the driver design, any ideas on how do I resolve the "ubi_io_read: error -74 (ECC error)" while mounting my UBIFS? Thanks, Vikram [1] http://www.linux-mtd.infradead.org/faq/ubi.html#L_ecc_error