public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Joshua Wise <joshua@joshuawise.com>, linux-mtd@lists.infradead.org
Subject: Re: JFFS2 NAND support - Mount failure on "good" filesystem
Date: Sun, 08 Feb 2004 09:58:58 +0100	[thread overview]
Message-ID: <200402080958.58584.tglx@linutronix.de> (raw)
In-Reply-To: <200402080113.36039.joshua@joshuawise.com>

On Sunday 08 February 2004 07:13, Joshua Wise wrote:
> Hi all,
>
> I am trying to get NAND flash working on the ipaq h1910.
>
> <7>jffs2_get_sb(): dev_name "/dev/mtdblock/1"
> <7>jffs2_get_sb(): path_lookup() returned 0, inode c9f411c0
> <7>jffs2_get_sb_mtd(): New superblock for device 1 ("h1910 NAND Flash")
> <7>JFFS2 using software ECC
> <7>Allocating readbuf of 16384 bytes
> <7>jffs2_scan_eraseblock(): Scanning block at 0x0
> <4>jffs2_check_nand_cleanmarker(): Block marked as failed at 00000000, fail
> count:175 <5>JFFS2: Erase block at 0x00000000 is not formatted. It will be
> erased <7>jffs2_scan_eraseblock(): Scanning block at 0x4000
> <4>jffs2_check_nand_cleanmarker(): Block marked as failed at 00004000, fail
> count:0 <5>JFFS2: Erase block at 0x00004000 is not formatted. It will be

Seems like you managed to corrupt the OOB area, as all your blocks are marked 
as bad. Your programming algorithm has to take care of the OOB data !
There are some slightly outdated docs on linux-mtd.infradead.org

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2004-02-08  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08  6:13 JFFS2 NAND support - Mount failure on "good" filesystem Joshua Wise
2004-02-08  8:58 ` Thomas Gleixner [this message]
2004-02-08 19:38   ` Joshua Wise

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=200402080958.58584.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=joshua@joshuawise.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