linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Vikram Narayanan <vikram186@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd_oobtest fails with GPMI-NAND
Date: Tue, 29 Jan 2013 10:06:28 +0800	[thread overview]
Message-ID: <51072EA4.7000201@freescale.com> (raw)
In-Reply-To: <5106AFAA.1020502@gmail.com>

于 2013年01月29日 01:04, Vikram Narayanan 写道:
> On 1/28/2013 8:50 AM, Huang Shijie wrote:
>> 于 2013年01月28日 10:39, Vikram Narayanan 写道:
>>> 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
Which mx6q' board are you using? the mx6q-arm2 or mx6q-ard?

The kernel only supports the mx6q-arm2 now.

>>>>> 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?
>>>> 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?
>>>
>> [1] what's the kernel's version?
>
> The above log is from 3.5.7, but the results are same for the latest 
> kernel (3.8-rc) too.
>
>> [2] what's type of the nand chips?
>>      could you show me the nand chip's geometry?
>
> Toshiba, 4 Gbit, (4096 +224) bytes ×64 pages ×2048blocks

The Toshiba's nand is not well supported by the kernel.
Are you sure the kernel parse out the correct geometry for the toshiba's 
nand?
Please recheck the page size and oob size with "mtdinfo /dev/mtd0".

thanks
Huang Shijie
> writesize - 4KiB
> oobsize - 224 bytes
>
> Regards,
> Vikram
>

  reply	other threads:[~2013-01-29  2:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 16:52 mtd_oobtest fails with GPMI-NAND Vikram Narayanan
2013-01-21  2:12 ` 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 [this message]
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=51072EA4.7000201@freescale.com \
    --to=b32955@freescale.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vikram186@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).