From: Zhonglin <zhonglinzh@mobilesoft.com.cn>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 Error or Maybe Flash Driver Error
Date: Wed, 28 Sep 2005 16:31:39 +0800 [thread overview]
Message-ID: <433A54EB.4060900@mobilesoft.com.cn> (raw)
Hi All,
I pulled the JFFS2 code from CVS. And Ported 2.6.12-omap1 to p2-sample.
When P2 sample run for a while, Sometimes The following message will show.
But when I boot again, it is ok again.
Does anybody meet the same problem ?
Node CRC 00800080 != calculated CRC 4bf2ff8d for node at 00676518
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9dfa60.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x0000059c)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9deb3c.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000f24)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9ddcbc.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000e80)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9dce64.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000e58)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9dbf3c.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000f28)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9db5dc.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000960)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9da914.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000cc8)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9d9c94.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000c80)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9d93c8.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x000008cc)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9d883c.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x00000b8c)
JFFS2 notice: (247) read_unknown: node header CRC failed at 0x9d7f74.
But it must have been OK earl.Node totlen on flash (0x00800080) !=
totlen from node ref (0x000008c8)
In our kernel source code, FILE drivers/mtd/chips/cfi_cmdset_0001.c ,
we change like below to fix a bug.
static void cfi_intelext_resume(struct mtd_info *mtd)
{
struct map_info *map = mtd->priv;
struct cfi_private *cfi = map->fldrv_priv;
int i;
struct flchip *chip;
for (i=0; i<cfi->numchips; i++) {
chip = &cfi->chips[i];
spin_lock(chip->mutex);
/* Go to known state. Chip may have been power cycled */
if (chip->state == FL_PM_SUSPENDED) {
//map_write(map, CMD(0xFF), cfi->chips[i].start); //@@@@@@@@@@@@@@@ It will report error!!!
map_write(map, CMD(0xFF), 0);
chip->oldstate = chip->state = FL_READY;
wake_up(&chip->wq);
}
spin_unlock(chip->mutex);
}
}
When our p2-sample enter the sleep mode, then resume , the resume code will be called.
So could anyone give me to fix the bug ??
Thanks a lot!
zhonglin
next reply other threads:[~2005-09-29 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 8:31 Zhonglin [this message]
2005-09-29 12:43 ` JFFS2 Error or Maybe Flash Driver Error Josh Boyer
2005-09-29 12:48 ` Artem B. Bityutskiy
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=433A54EB.4060900@mobilesoft.com.cn \
--to=zhonglinzh@mobilesoft.com.cn \
--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