From: Orjan Friberg <of@flatfrog.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Spurious ECC errors with mtd_subpagetest (OMAP3, NAND)
Date: Fri, 2 Mar 2012 17:42:10 +0100 [thread overview]
Message-ID: <4F50F862.5030305@flatfrog.com> (raw)
In-Reply-To: <4F50F2AB.10209@flatfrog.com>
On 03/02/2012 05:17 PM, Orjan Friberg wrote:
> Hi,
>
> When running the mtd_subpagetest I'm seeing more or less spurious ECC
> corrections. I.e., one round may show 4 corrections and the next will
> show 7, only some of which are the same as the previous 4.
FWIW
* I'm seeing the same behaviour (i.e. transient ECC errors) when doing
nanddump on a partition.
* mtd_oobtest fails on "verify failed at <varying address>", and "read
past end of device".
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2012-03-02 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 16:17 Spurious ECC errors with mtd_subpagetest (OMAP3, NAND) Orjan Friberg
2012-03-02 16:42 ` Orjan Friberg [this message]
2012-03-02 17:17 ` Grazvydas Ignotas
2012-03-05 8:13 ` Orjan Friberg
2012-03-05 8:56 ` Matthieu CASTET
2012-03-05 9:09 ` Orjan Friberg
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=4F50F862.5030305@flatfrog.com \
--to=of@flatfrog.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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).