public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Andriy Korud" <a.korud@vector.com.pl>
To: <linux-mtd@lists.infradead.org>
Subject: Unmarking bad blocks?
Date: Mon, 7 Jun 2004 20:54:36 +0200	[thread overview]
Message-ID: <80908CC5B2C9DB47AAF8C77892FCB44315F7AD@lion.vector.com.pl> (raw)

Hi,
after playing with mkfs.jffs2 and nandwrite a lot of blocks on my flash chip (Samsung 128Mb) become marked as bad (and I'm sure they were not bad at the beginning).
Is it possible to 'unmark' them or should this chip is unusble anymore?
flash_eraseall gives:

nand_erase: attempt to erase a bad block at page 0x00000000
nand_erase: attempt to erase a bad block at page 0x00000040
nand_erase: attempt to erase a bad block at page 0x00000080
nand_erase: attempt to erase a bad block at page 0x000000c0
...

Even I commented out bad block checking in nand_erase(), flash_eraseall comlete successfully however blocks remain marked as bad.

Any ideas?

Thanks in advance,

--

Andriy Korud

             reply	other threads:[~2004-06-07 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 18:54 Andriy Korud [this message]
2004-06-07 22:10 ` Unmarking bad blocks? 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=80908CC5B2C9DB47AAF8C77892FCB44315F7AD@lion.vector.com.pl \
    --to=a.korud@vector.com.pl \
    --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