From: Vikram Narayanan <vikram186@gmail.com>
To: linux-mtd@lists.infradead.org
Cc: Huang Shijie <b32955@freescale.com>
Subject: mtd_oobtest fails with GPMI-NAND
Date: Fri, 18 Jan 2013 22:22:05 +0530 [thread overview]
Message-ID: <50F97DB5.7040801@gmail.com> (raw)
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
<drivers/mtd/nand/gpmi-nand/gpmi-nand.c>
Is there a way to run this test successfully?
Regards,
Vikram
next reply other threads:[~2013-01-18 16:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 16:52 Vikram Narayanan [this message]
2013-01-21 2:12 ` mtd_oobtest fails with GPMI-NAND Huang Shijie
2013-01-28 2:39 ` Vikram Narayanan
2013-01-28 3:20 ` Huang Shijie
2013-01-28 17:04 ` Vikram Narayanan
2013-01-29 2:06 ` Huang Shijie
2013-01-29 2:26 ` Vikram Narayanan
2013-01-29 2:36 ` Huang Shijie
2013-01-29 16:28 ` Vikram Narayanan
2013-01-30 2:27 ` Huang Shijie
2013-02-02 6:41 ` Vikram Narayanan
2013-02-02 7:42 ` Huang Shijie
2013-02-02 7:46 ` Huang Shijie
2013-05-08 14:33 ` Stefan Roese
2013-05-09 12:30 ` Vikram Narayanan
2013-05-10 6:20 ` Stefan Roese
2013-05-12 12:10 ` Vikram Narayanan
2013-05-12 15:09 ` Stefan Roese
2013-05-13 16:38 ` Vikram Narayanan
2013-05-13 2:51 ` Huang Shijie
2013-05-13 8:01 ` Stefan Roese
2013-05-13 9:01 ` Huang Shijie
2013-05-13 9:22 ` Stefan Roese
2013-05-13 9:34 ` Huang Shijie
2013-05-13 10:02 ` Stefan Roese
2013-05-14 2:09 ` Huang Shijie
2013-05-14 2:11 ` Huang Shijie
2013-05-13 16:51 ` Vikram Narayanan
2013-05-14 2:23 ` Huang Shijie
2013-05-14 2:33 ` Vikram Narayanan
2013-05-14 2:47 ` Huang Shijie
2013-05-13 16:43 ` Vikram Narayanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F97DB5.7040801@gmail.com \
--to=vikram186@gmail.com \
--cc=b32955@freescale.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.