From: "Mike Hench" <mhench@elutions.com>
To: "Scott Wood" <scottwood@freescale.com>,
"Matthew L. Creech" <mlcreech@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org
Subject: RE: NAND BBT corruption on MPC83xx
Date: Sat, 18 Jun 2011 13:55:01 -0400 [thread overview]
Message-ID: <F87D23B7E1F84E4AB52E4FA4A55F85DC0259E343@tpamail.elutions.com> (raw)
In-Reply-To: <20110617163442.204348a0@schlenkerla.am.freescale.net>
Scott Wood wrote:
> As for the corruption, could it be degradation from repeated reads of
that
> one page?
Read Disturb. I Did not know SLC did that.
It just takes 10x as long as MLC, on the order of a million reads.
Supposedly erasing the block fixes it.
It is not a permanent damage thing.
I was seeing ~9 hours before failure with heavy writes.
~4GByte/hour =3D 2M pages, total ~18 million reads before errors in that
last block showed up.
Cool. Now we know.
Thanks.
Mike Hench
next prev parent reply other threads:[~2011-06-18 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 20:54 NAND BBT corruption on MPC83xx Matthew L. Creech
2011-06-17 21:34 ` Scott Wood
2011-06-18 17:55 ` Mike Hench [this message]
2011-06-20 11:22 ` Atlant Schmidt
2011-06-23 8:31 ` Artem Bityutskiy
2011-06-20 15:20 ` Matthew L. Creech
2011-07-05 19:58 ` Matthew L. Creech
2011-07-05 19:59 ` [PATCH] mtd: eLBC NAND: remove bogus ECC read-back Matthew L. Creech
2011-07-05 20:15 ` Scott Wood
2011-07-05 22:35 ` [PATCH v2] mtd: eLBC NAND: remove elbc_fcm_ctrl->oob_poi Matthew L. Creech
2011-07-05 23:01 ` Scott Wood
2011-07-05 23:14 ` Matthew L. Creech
2011-07-05 23:14 ` [PATCH v3] " Matthew L. Creech
2011-07-06 7:23 ` Artem Bityutskiy
2011-07-11 15:30 ` NAND BBT corruption on MPC83xx Matthew L. Creech
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=F87D23B7E1F84E4AB52E4FA4A55F85DC0259E343@tpamail.elutions.com \
--to=mhench@elutions.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mlcreech@gmail.com \
--cc=scottwood@freescale.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).