All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Janot <f.janot@ateme.fr>
To: linux-mtd@lists.infradead.org
Subject: jffs2_get_inode_nodes(): Data CRC failed on NAND chip
Date: Mon, 17 May 2004 17:48:31 +0200	[thread overview]
Message-ID: <1084808911.1659.20.camel@localhost> (raw)

Hi,

I've got a problem when using jffs2 filesystem on a nand flash device.

I've created a root file system image on my pc (little-endian) from
/rootfs directory which contain all needed files. I burn this image into
a nand flash (samsung k9f5608 - 32MB nand with 512+16 bytes per pages)
on a board with a power pc processor (big-endian).

So, on the pc, i do :
# mkfs.jffs2 -p --root=/rootfs -e 16384 -b -o fs_img

My flash partitions are :
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00004000 "Nand Flash Kernel"
mtd1: 01a00000 00004000 "Nand Flash RootFS"
mtd2: 00200000 00004000 "Nand Flash Test"

On my target, from an nfs mount root file system, i do :
# nandwrite -j /dev/mtd1 /fs_img

After that, I reboot my board and make the kernel boot from nand root
file system. The first boot is ok but when i reboot one more time, I
have the following message :
Empty flash at 0x0047b900 ends at 0x0047ba00
jffs2_get_inode_nodes(): Data CRC failed on node at 0x015fc000: Read
0x5a62bf55, calculated 0x349968c2

And each time I reboot, there is one message more. (I do nothing else
than login and reboot)
Empty flash at 0x0047b900 ends at 0x0047ba00
Empty flash at 0x015fc268 ends at 0x015fc400
jffs2_get_inode_nodes(): Data CRC failed on node at 0x015fc000: Read
0x5a62bf55, calculated 0x349968c2
jffs2_get_inode_nodes(): Data CRC failed on node at 0x015fc778: Read
0xdf13fb17, calculated 0xbdff7e75

etc ...

Do you have any idea on what happens ?

Thanks

Frederic Janot

             reply	other threads:[~2004-05-17 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 15:48 Frederic Janot [this message]
2004-05-18 10:20 ` jffs2_get_inode_nodes(): Data CRC failed on NAND chip Simon Haynes

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=1084808911.1659.20.camel@localhost \
    --to=f.janot@ateme.fr \
    --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.