All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leo (Hao) Chen" <leochen@broadcom.com>
To: "Saurabh Kadekodi" <saurabhkadekodi@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Problem with nand flash while booting 2.6.30
Date: Wed, 12 Aug 2009 10:17:13 -0700	[thread overview]
Message-ID: <20090812171713.GA5076@broadcom.com> (raw)
In-Reply-To: <967093cd0908120036q51283790se400dc08219daed@mail.gmail.com>

On Wed, Aug 12, 2009 at 12:36:53AM -0700, Saurabh Kadekodi wrote:
> 
> Then later it gives a lot of ECC errors and prints the following messages:
> 
> 
> Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
> > empty_blocks 0, bad_blocks 208, c->nr_blocks 438
> > VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)
> > Please append a correct "root=" boot option; here are the available partitions:
> > 1f00             256 mtdblock0 (driver?)
> > 1f01            2048 mtdblock1 (driver?)
> > 1f02          112128 mtdblock2 (driver?)
> > 1f03             512 mtdblock3 (driver?)
> > b300         2008064 mmcblk0 driver: mmcblk
> >   b301           31288 mmcblk0p1

You may try to re-burn the rootfs to your flash.  I had experienced
similar problem when I switched my kernel from 2.6.27 to 2.6.30.  I
don't know the exact reason, but the ECC algorithm or something may have been changed.


-- 
Leo Hao Chen
Software Engineer
Broadcom Canada Inc.

      parent reply	other threads:[~2009-08-12 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12  7:36 Problem with nand flash while booting 2.6.30 Saurabh Kadekodi
2009-08-12 15:12 ` Mike Rapoport
     [not found]   ` <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com>
2009-08-13  5:25     ` Mike Rapoport
2009-08-13  7:12       ` Saurabh Kadekodi
2009-08-12 17:17 ` Leo (Hao) Chen [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=20090812171713.GA5076@broadcom.com \
    --to=leochen@broadcom.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=saurabhkadekodi@gmail.com \
    /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.