From: Thomas Gleixner <tglx@linutronix.de>
To: Pantelis Antoniou <panto@intracom.gr>, linux-mtd@lists.infradead.org
Subject: Re: NAND write verify failed problem
Date: Wed, 04 Jun 2003 20:16:01 +0200 [thread overview]
Message-ID: <200306042016.01366.tglx@linutronix.de> (raw)
In-Reply-To: <3EDB2F4E.6050502@intracom.gr>
On Monday 02 June 2003 13:04, Pantelis Antoniou wrote:
>
> > root$ fcp -v /tmp/root.jffs2.image /dev/mtd0
> > Erasing blocks: 33/33 (100%)
> > Writing data: 528k/528k (100%)
> > Verifying data: 20k/528k (3%)File does not seem to match flash data.
Are you writing with ECC ? If not use nandwrite from mtd/utils
> Mount takes 30 seconds to finish, and during that time the board does not
> respond to any external stimulus. This is caused I believe from the scaning
> of the NAND, which I take it is normal.
Should be much faster with current MTD CVS code
> nand_write_page: Failed write verify, page 0x0000040b <5>Write of 68
> bytes at 0x00081774 failed. returned -5, retlen 0
> Mar 10 21:44:22 netvia-ppc kernel: Not marking the space at 0x00081774
> as dirty because the flash driver returned retlen zero
> Any ideas how to proceed?
Yes, update nand driver from MTD-CVS. It's fixed.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2003-06-04 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 11:04 NAND write verify failed problem Pantelis Antoniou
2003-06-02 11:21 ` NAND write verify failed problem (SOLVED?) Pantelis Antoniou
2003-06-04 18:16 ` Thomas Gleixner [this message]
2003-06-05 7:31 ` NAND write verify failed problem Pantelis Antoniou
2003-06-05 21:10 ` NAND write verify failed problem -->cramfs Charles Manning
2003-06-06 9:54 ` Kevin Liao
2003-06-07 20:34 ` Charles Manning
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=200306042016.01366.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=panto@intracom.gr \
/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.