public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Guido Martínez" <guido@vanguardiasur.com.ar>,
	"Artem Bityutskiy" <dedekind1@gmail.com>
Subject: Problems in Out of tree TI SDK omap2-nand driver (Re: [PATCH 3/3] nandtest: Introduce multiple reads & check iterations)
Date: Mon, 5 May 2014 09:50:47 -0300	[thread overview]
Message-ID: <20140505125047.GA11106@arch.cereza> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EACA6B9@DBDE04.ent.ti.com>

I've changed the subject of this mail, since it seems we've moved from the
discussion.

On 05 May 10:58 AM, Gupta, Pekon wrote:
> 
> However, I know of some issues in OMAP NAND driver bundled with
> 3.2 kernel, which might be helpful in nailing down your specific issue.
> 

FWIW, I'm not using such driver anymore. Right after spotting this, we've
ran the *same* test on the mainline driver, which passed. This was the kick
we needed to start using mainline (we also need mainline for other reasons).

> (1) 3.2 kernel does not have concept of bitflip_threshold, so by default
> scrubbing and peb_torture happens even for single bit-flips. So please
> pull-in following patch series.
> [PATCH v2 0/7] mtd: Change meaning of -EUCLEAN return code on reads
> http://lists.infradead.org/pipermail/linux-mtd/2012-April/040945.html
> 

Isn't this series related to the higher-level treatment of bitflips?
In that case, it's not related to the issue I got. Keep in mind that
this simple test failed in our v3.2 stress (using this nandtest patch):

  * erase
  * write
  * read
  * read
  * ...
  * read (20 times)

> (2) OMAP NAND in 3.2 kernel does not factor bit-flips in empty pages
> Hence if empty pages with bit-flips are encountered, then it treats them
> like programmed pages and expects a ECC correction on them. But as
> empty pages do not have ECC stored in OOB, the driver bails out giving
> 'uncorrectable ecc' read errors.
> 

Since the test doesn't involve empty pages, I'd say this is not relevant.

If you're still interested in debugging the problematic TI SDK omap2-nand
driver, I suggest that you try using this nandtest patch and see how it
goes.

Despite you saying drivers can fail the test, I think it's still a nice test.
Keep in mind the nandtest tool reports the number of corrected ECC errors
after reads, so if that number is adding-up and increasing you can even
use this patch to see this evolution.

All in all, I think it's still a nice improvement on stock nandtest.
-- 
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar

  parent reply	other threads:[~2014-05-05 12:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 13:14 [PATCH 0/3] nandtest: Allow multiple read & check iterations Ezequiel Garcia
2014-04-28 13:14 ` [PATCH 1/3] nandtest: Remove redundant check Ezequiel Garcia
2014-05-05  7:30   ` Artem Bityutskiy
2014-04-28 13:14 ` [PATCH 2/3] nandtest: Move the "read and compare" code to a function Ezequiel Garcia
2014-05-05  7:36   ` Artem Bityutskiy
2014-04-28 13:14 ` [PATCH 3/3] nandtest: Introduce multiple reads & check iterations Ezequiel Garcia
2014-05-05  7:35   ` Artem Bityutskiy
2014-05-05  9:56     ` Ezequiel García
2014-05-05 10:07   ` Gupta, Pekon
2014-05-05 10:33     ` Ezequiel Garcia
2014-05-05 10:58       ` Gupta, Pekon
2014-05-05 11:09         ` Artem Bityutskiy
2014-05-05 11:21           ` Gupta, Pekon
2014-05-05 12:50         ` Ezequiel Garcia [this message]
2014-05-05 18:12           ` Problems in Out of tree TI SDK omap2-nand driver (Re: [PATCH 3/3] nandtest: Introduce multiple reads & check iterations) Gupta, Pekon
2014-05-30 23:49             ` Brian Norris

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=20140505125047.GA11106@arch.cereza \
    --to=ezequiel@vanguardiasur.com.ar \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=guido@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.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