From: Artem Bityutskiy <dedekind1@gmail.com>
To: Subodh Nijsure <snijsure@grid-net.com>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: What would cause large block of NAND to be marked as bad?
Date: Mon, 07 May 2012 21:56:49 +0300 [thread overview]
Message-ID: <1336417009.2041.4.camel@koala> (raw)
In-Reply-To: <4FA80EEB.8040501@grid-net.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Mon, 2012-05-07 at 11:05 -0700, Subodh Nijsure wrote:
> Hello,
>
> I am working with some prototype hardware and I have seen some weird
> behaviour when testing power cut.
>
> On my board I have Micron MT29F2G08ABAEAH4 part and now have three
> boards on which close to 20-30 blocks have been marked as bad.
>
> We mainly run UBIFS on these boards, if there was flash data corruption
> we expected to see errors at UBIFS level i.e. not able to mount UBIFS
> file system but we didn't expect NAND blocks themselves to be marked as
> bad, due to power cut.
>
> What would cause large number of NAND blocks to be marked as bad, due to
> power cut?
Did you look at Mike Dunn's bitflip_threshold stuff? It is in my
l2-mtd.git tree. Look at this patch and the next ones from Mike:
http://git.infradead.org/users/dedekind/l2-mtd.git/commit/be1bb4ef1f98059f9d54623f3ed01423095fa967
Commit messages contain descriptions and references. May be for your
flash you need to set higher threshold?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-07 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 18:05 What would cause large block of NAND to be marked as bad? Subodh Nijsure
2012-05-07 18:56 ` Artem Bityutskiy [this message]
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=1336417009.2041.4.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=snijsure@grid-net.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).