From: Mike Dunn <mikedunn@newsguy.com>
To: linux-mtd@lists.infradead.org
Subject: ubi on MLC nand flash
Date: Sun, 06 Nov 2011 07:24:24 -0800 [thread overview]
Message-ID: <4EB6A6A8.7010703@newsguy.com> (raw)
Hi everyone,
I recently started to do serious testing of UBI on the diskonchip G4 MLC nand
driver I'm finishing up. I started with the io_basic ubi test in mtd-utils.
What I find is that, after a few minutes, enough PEBs are marked as bad to
exhaust the reserve PEB pool, UBI switches to r/o mode, and the test fails. The
reason is that - on this device at least - bit flips seem to be persistent;
i.e., you will get e.g. 1 bit flip every time you read a certain page.
Consequently, when the bit flip occurs and the PEB gets scrubbed, the torture
test fails because the bit flip reoccurs, and the PEB is marked bad.
I expected that eventually I might have to dig into the "program disturb",
"read-disturb" or "paired pages" MLC issues, but the problem seems more
fundamental. My general impression is that UBI is too unforgiving for this
device. The ecc can correct up to 4 bit flips, so 1 bit flip seems to not be a
big deal. I'm new to UBI so this is not a critique or a proposal, I'm just
hoping some experts can offer some advice or opinions. The obvious remedy is to
set a higher threshold for marking a PEB as bad, say 2 or 3 bit flips.
Thanks,
Mike
next reply other threads:[~2011-11-06 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 15:24 Mike Dunn [this message]
2011-11-06 17:35 ` ubi on MLC nand flash Ivan Djelic
2011-11-06 20:28 ` Mike Dunn
2011-11-08 21:45 ` Artem Bityutskiy
2011-11-09 3:04 ` Mike Dunn
2011-11-09 8:44 ` Artem Bityutskiy
2011-11-09 13:13 ` Mike Dunn
2011-11-09 12:22 ` Artem Bityutskiy
2011-11-08 21:32 ` Artem Bityutskiy
2011-11-09 1:51 ` Mike Dunn
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=4EB6A6A8.7010703@newsguy.com \
--to=mikedunn@newsguy.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.