All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Haynes <simon@baydel.com>
To: tglx@linutronix.de, Michael Moedt <xemc@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad Blocks On JFFS2/NAND
Date: Wed, 20 Oct 2004 10:40:41 +0100	[thread overview]
Message-ID: <E4E1C5BE221F@baydel.com> (raw)
In-Reply-To: <1098222917.12223.1020.camel@thomas>


This 5 error business is only if you have relatively new code. Old code 
generates an incorrect and permanent bad block after 1 failure. I am testing 
the suggestion by Thomas that this is a page cache problem by always marking 
an erase page as invalid. No errors as yet but I will keep you posted.

Cheers

Simon.

On Tuesday 19 Oct 2004 10:55 pm, Thomas Gleixner wrote:
> 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
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2004-10-20  9:48 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
2004-10-20  9:40       ` Simon Haynes [this message]
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=E4E1C5BE221F@baydel.com \
    --to=simon@baydel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    --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 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.