public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Arvind Agrawal" <arvind@4access-comm.com>
To: <linux-mtd@lists.infradead.org>
Subject: Nand Read Errors using Jffs2
Date: Thu, 14 Sep 2006 18:28:58 -0700	[thread overview]
Message-ID: <00fa01c6d866$51306df0$6501a8c0@arvindwin2000> (raw)

Hi,

We are using Micro Nand Flash 256MiB with Arm Linux 2.6.11.7 (which is more
than a year old) .
Time to time , I get mtd->read errors but most of the time data seems to be
O.K. and then will start getting inode errors.
Also the flash started it with just 3 bad blocks and now I have around 12
bad blocks, which means that either they have gone genuinely bad or because
of excessive read errors jffs2 marked them bad ;

# # time cp stage.jffs2 nand4/s14%

mtd->read(0x1044 bytes from 0x2f1c888) returned ECC error
Header CRC failed on REF_PRISTINE node at 0x02f1c888: Read 0x30303030,
calculated 0xa52a526a

# # time cp stage.jffs2 nand4/s10_1

mtd->read(0x1044 bytes from 0x2f0e558) returned ECC error
Unknown node type for REF_PRISTINE node at 0x02f0e558: 0x0000

# time cp stage.jffs2 nand4/s41_7
mtd->read(0x1000 bytes from 0x2f20000) returned ECC error
Newly-erased block contained word 0x30 at offset 0x02f20000
mtd->read(0x1000 bytes from 0x2f20000) returned ECC error
Newly-erased block contained word 0x0 at offset 0x02f20000


I need help to figure out that what may be causing this problem?
Could it be hardware timing related?
Or could point software, either old versions of mtd, jffs2 or the small
driver , we did for Micron NAND?

Any pointers are greatly appreciated.

thanks,
Arvind

                 reply	other threads:[~2006-09-15  2:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='00fa01c6d866$51306df0$6501a8c0@arvindwin2000' \
    --to=arvind@4access-comm.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