From: Mike Dunn <mikedunn@newsguy.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Problems with mtd_oobtest
Date: Wed, 29 Feb 2012 08:06:51 -0800 [thread overview]
Message-ID: <4F4E4D1B.4000903@newsguy.com> (raw)
In-Reply-To: <CAHMF36Gy9r2mPRrahpbAMvwOE=jWD3jzWqpF4846gG6saHjZ-w@mail.gmail.com>
On 02/27/2012 11:02 PM, Matej Kupljen wrote:
> I can run mtd_speedtest, mtd_stresstest, mtd_readtest, mtd_pagetest without the
> problems, but when I start the mtd_oobtest it fails, basically on every page!
Your flash device probably does not support writing oob-only. This is true of
some NAND devices. I wouldn't worry about this test. This failure is probably
unrelated to your ubifs problems.
> I can use JFFS2 on this device, and for some time even UBIFS, but then
> it just fails.
What is the nature of the ubifs failure? The kernel log should tell you. It
may be the same problem I experience, where over time too many erase bocks are
marked as bad. This is due to the unforgiving nature of ubi wrt corrected
bitflips, and tends to be a problem on NAND flash devices with high bit errors,
for which the device compensates with strong ecc. I'm working on some patches
that should fix this.
Mike
next prev parent reply other threads:[~2012-02-29 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 7:02 Problems with mtd_oobtest Matej Kupljen
2012-02-29 16:06 ` Mike Dunn [this message]
2012-03-09 10:35 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 12:16 Matej Kupljen
2012-03-03 1:19 ` Mike Dunn
2012-03-09 12:13 ` Artem Bityutskiy
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=4F4E4D1B.4000903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox