From: Thomas Gleixner <tglx@linutronix.de>
To: llandre <r&d@wawnet.biz>, linux-mtd@lists.infradead.org
Subject: Re: Help to understand error messages (MTD on Samsung NAND chips)
Date: Thu, 31 Jul 2003 20:56:00 +0200 [thread overview]
Message-ID: <200307312056.00480.tglx@linutronix.de> (raw)
In-Reply-To: <5.1.1.6.0.20030731180128.024a0020@192.168.2.1>
On Thursday 31 July 2003 18:16, llandre wrote:
> Hi Thomas,
>
> sorry for this late response, but I had to work for a couple of weeks on
> another project.
>
> Anyway I restored the original source files included in the kernel and I
> collected the debug information printed during the execution of the
> eraseall command.
> Here is a short dump of what I got:
>
> ---------------------------------------------------------------------------
>------------ bash-2.05# echo 9 >/proc/sys/kernel/printk
> bash-2.05# eraseall /dev/mtd0
> MTD_open
> MTD_ioctl
> Erasing 16 KibyMTD_ioctl
> te @ 0 -- 0 % cnand_erase: start = 0x00000000, len = 16384
> omplete.nand_erase: attempt to erase a bad block at page 0x00000000
Byte 5 of the OOB area in the first page of the block is != 0xFF.
That means, that this block is bad. Either it was set by the manufacturer,
which is possible as NAND chips can contain bad blocks, or JFFS2 / YAFFS do
it when they recognize a bad block, or you managed it anyhow to write the bad
block markers. I assume the latter.
Bad blocks may not be erased, as the bad block information may be destroyed
and you then would use a bad block for storing data.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-07-31 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 16:39 Help to understand error messages (MTD on Samsung NAND chips) llandre
2003-07-15 17:45 ` Thomas Gleixner
2003-07-16 8:51 ` llandre
2003-07-16 22:34 ` David Woodhouse
2003-07-31 16:16 ` llandre
2003-07-31 18:56 ` Thomas Gleixner [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=200307312056.00480.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=r&d@wawnet.biz \
/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.