From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Moedt <xemc@yahoo.com>
Cc: linux-mtd@lists.infradead.org, simon@baydel.com
Subject: Re: Bad Blocks On JFFS2/NAND
Date: Tue, 19 Oct 2004 23:55:17 +0200 [thread overview]
Message-ID: <1098222917.12223.1020.camel@thomas> (raw)
In-Reply-To: <20041019214518.26339.qmail@web52703.mail.yahoo.com>
On Tue, 2004-10-19 at 23:45, Michael Moedt wrote:
> 1. Do you know what usually causes the "Newly-erased block contained
> word "... error?
> Is it caused by a interrupted (or otherwise failed) erase? Would
> power-fail cause this?
It's caused by a failed erase. If the chip interface is correct then it
is usually a problem of a bad page/block. If not (e.g. wrong timing) it
might return too early from an erase.
> 2. Would this cause good blocks to be incorrectly [and permanently]
> marked as bad?
Only if failes 5 times after mount. The counter is reset with each
mount.
>
> I think I may have seen something similar on my system. I'm
> considering writing a test to see if this is a problem for me, but
> I'd like to learn more about this also.
Which version of the mtd/nand code ?
There was a problem with the page cache, which was not invalidated on
erase some time ago, but its fixed.
tglx
next prev parent reply other threads:[~2004-10-19 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 11:22 Bad Blocks On JFFS2/NAND Simon Haynes
2004-10-19 11:50 ` Thomas Gleixner
2004-10-19 14:39 ` Simon Haynes
2004-10-19 15:02 ` Thomas Gleixner
2004-10-19 15:18 ` Simon Haynes
2004-10-19 21:45 ` Michael Moedt
2004-10-19 21:55 ` Thomas Gleixner [this message]
2004-10-20 9:40 ` Simon Haynes
2004-10-20 9:53 ` Thomas Gleixner
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=1098222917.12223.1020.camel@thomas \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=simon@baydel.com \
--cc=xemc@yahoo.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