All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Gatliff <bgat@billgatliff.com>
To: linux-mtd@lists.infradead.org
Subject: Node CRC failures in latest mainline git?
Date: Wed, 30 Jul 2008 23:25:07 -0500	[thread overview]
Message-ID: <48913EA3.9080603@billgatliff.com> (raw)

Guys:


I pulled from Linus' tree yesterday, and all of a sudden I'm seeing a _ton_ of
these:

JFFS2 notice: (224) jffs2_get_inode_nodes: Node header CRC failed at 0x263a0fc.
{1985,c002,00000046,32fe3396}

An older kernel (three or four weeks ago) continues to work fine on the same board.

The target is a PXA270 with a Spansion 29GL512N.  The kernel was built with
arm-linux-gnueabi-gcc (GCC) 4.2.4 (Debian 4.2.4-3).  There haven't been any
changes in the mtd-related parts of the kernel, other than what's come in from
Linus.

It looks like the most recent mtd-related commit is this:

$ git-log drivers/mtd
commit 9ee08c2df47c10ba624ff05a6c0f2500748bcb69
Merge: eaf0ba5... 3d45955...
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jul 26 20:30:56 2008 -0700

    Merge git://git.infradead.org/mtd-2.6

    * git://git.infradead.org/mtd-2.6: (57 commits)
      [MTD] [NAND] subpage read feature as a way to increase performance.
      CPUFREQ: S3C24XX NAND driver frequency scaling support.
      [MTD][NAND] au1550nd: remove unused variable
      [MTD] jedec_probe: Fix SST 16-bit chip detection
      [MTD][MTDPART] Fix a division by zero bug
      [MTD][MTDPART] Cleanup and document the erase region handling
      [MTD][MTDPART] Handle most checkpatch findings
      [MTD][MTDPART] Seperate main loop from per-partition code in add_mtd_partiti
      [MTD] physmap: resume already suspended chips on failure to suspend
      [MTD] physmap: Fix suspend/resume/shutdown bugs.
      [MTD] [NOR] Fix -ETIMEO errors in CFI driver
      [MTD] [NAND] fsl_elbc_nand: fix section mismatch with CONFIG_MTD_OF_PARTS=y
      [JFFS2] Use .unlocked_ioctl
      [MTD] Fix const assignment in the MTD command line partitioning driver
      [MTD] [NOR] gen_probe: No debug message when debugging is disabled
      [MTD] [NAND] remove __PPC__ hardcoded address from DiskOnChip drivers
      [MTD] [MAPS] Remove the bast-flash driver.
      [MTD] [NAND] fsl_elbc_nand: ecclayout cleanups
      [MTD] [NAND] fsl_elbc_nand: implement support for flash-based BBT
      [MTD] [NAND] fsl_elbc_nand: fix OOB workability for large page NAND chips
      ...


Were I more competent with git, I would figure out how to bisect down to the
patch that caused the problem.  That's still a bit out of my skillset at the
moment, unfortunately--- I've done bisects successfully in the past, but for
some reason I just can't get git to play along this time...


Thanks!


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com

             reply	other threads:[~2008-07-31  4:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  4:25 Bill Gatliff [this message]
2008-07-31  4:44 ` Node CRC failures in latest mainline git? Bill Gatliff
2008-08-01 20:59   ` David Woodhouse
2008-08-01 21:01     ` Bill Gatliff
2008-08-01 21:14       ` David Woodhouse
2008-07-31  4:56 ` David Brown
2008-07-31 20:28   ` Bill Gatliff
2008-08-01  2:47     ` David Brown
2008-08-01  3:48       ` Bill Gatliff

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=48913EA3.9080603@billgatliff.com \
    --to=bgat@billgatliff.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 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.