All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan McDowell <noodles@earth.li>
To: linux-mtd@lists.infradead.org
Subject: Re: 2.6.18-rc4 jffs2 problems
Date: Thu, 10 Aug 2006 07:04:09 +0100	[thread overview]
Message-ID: <20060810060409.GH27094@earth.li> (raw)
In-Reply-To: <20060809093419.GA14187@earth.li>

On Wed, Aug 09, 2006 at 10:34:19AM +0100, Jonathan McDowell wrote:
> On Mon, Aug 07, 2006 at 07:41:50PM +0100, Richard Purdie wrote:
> > I previous reported problems with jffs2 on the Zaurus. I tested
> > 2.6.18-rc4 and nothing has changed - I see the following when booting,
> > both with filesystems that work with 2.6.17 and freshly reflashed
> > systems:
> > 
> > Linux version 2.6.18-rc4-.dev-snapshot-20060807 (richard@tim) (gcc version 3.4.3) #1 PREEMPT Mon Aug 7 17:47:07 BST 2006
> > CPU: XScale-PXA250 [69052904] revision 4 (ARMv5TE), cr=0000397f
> > Machine: SHARP Poodle
> > [...]
> > Sharp SL series flash device: 800000@0
> > Using static partision definition
> > Creating 1 MTD partitions on "sharpsl-flash":
> > 0x00120000-0x007f0000 : "Boot PROM Filesystem"
> > NAND device: Manufacturer ID: 0x98, Chip ID: 0x76 (Toshiba NAND 64MiB 3,3V 8-bit)
> > Scanning device for bad blocks
> > Creating 3 MTD partitions on "sharpsl-nand":
> > 0x00000000-0x00700000 : "System Area"
> > 0x00700000-0x01d00000 : "Root Filesystem"
> > 0x01d00000-0x04000000 : "Home Filesystem"
> > [...]
> > Empty flash@0x0054bc5c ends at 0x0054be00
> > VFS: Mounted root (jffs2 filesystem) readonly.
> > Freeing init memory: 100K
> > JFFS2 error: (472) jffs2_get_inode_nodes: short read@0x074e84: 68 instead of 380.
> > JFFS2 error: (472) jffs2_do_read_inode_internal: cannot read nodes for ino 153, returned error is -5
> 
> I'm seeing similar problems on the Amstrad Delta, both with a filesystem
> that works fine under 2.6.16 and a completely clean fs. Like the Zaurus
> this is a NAND device.

A "git bisect" is flagging up 8593fbc68b0df1168995de76d1af38eb62fd6b62
as the problem commit:

commit 8593fbc68b0df1168995de76d1af38eb62fd6b62
Author: Thomas Gleixner <tglx@cruncher.tec.linutronix.de>
Date:   Mon May 29 03:26:58 2006 +0200

    [MTD] Rework the out of band handling completely

J.

-- 
                                            jid: noodles@jabber.earth.li
101 things you can't have too much of : 25
                                            - email.

  reply	other threads:[~2006-08-10  6:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 18:41 2.6.18-rc4 jffs2 problems Richard Purdie
2006-08-08  6:40 ` Andrew Morton
2006-08-08  7:15 ` Artem B. Bityutskiy
2006-08-09  9:34 ` Jonathan McDowell
2006-08-10  6:04   ` Jonathan McDowell [this message]
2006-08-10  9:29     ` Artem B. Bityutskiy
2006-08-15 22:29     ` Richard Purdie
2006-08-17 22:09 ` Richard Purdie
2006-08-20  1:34   ` Josh Boyer
2006-08-20  1:34     ` Josh Boyer
2006-08-21  1:35     ` Greg KH
2006-08-21  1:35       ` Greg KH
2006-08-22 14:12       ` David Woodhouse
2006-08-22 14:12         ` David Woodhouse
2006-08-22 14:39         ` Josh Boyer
2006-08-22 14:39           ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2006-08-08  8:07 Koeller, T.

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=20060810060409.GH27094@earth.li \
    --to=noodles@earth.li \
    --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 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.