From: "zhang hao" <zh_chaohao@hotmail.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2 problem
Date: Wed, 09 Jun 2004 06:57:55 +0000 [thread overview]
Message-ID: <BAY13-F53EymQtczmul0003ee3c@hotmail.com> (raw)
Hi,
I use kernel 2.4.18 and mtd-snapshot-20030110. My flash is 16M AMD/Fujitsu
flash.I update cfi_cmdset_0002.c from v1.61 to 1.63.
My partitions is:
bootloader 16k
kernel 2032k
rootfs 6M
If I boot up the board, problem appears like this:
"...........................................
Empty flash at 0x002fdffc ends at 0x002fe000
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 40k freed
init-2.05a# mount -t jffs2 /dev/mtdblock2 /tmp
Waiting for write to complete timed out in do_write_oneword.<5>Write of 68
bytes at 0x002fe
514 failed. returned -5, retlen 0
Not marking the space at 0x002fe514 as dirty because the flash driver
returned retlen zero
can't create lock file /etc/mtab~9: Input/output error (use -n flag to
override)
init-2.05a# cd bin
Node CRC 27c9a666 != calculated CRC 3a68bebd for node at 0003567c
Node CRC 277ca666 != calculated CRC eab325e6 for node at 00035e18
Node CRC 27cea666 != calculated CRC 70c74bd7 for node at 000366bc
Node CRC 2784a666 != calculated CRC 44fe4247 for node at 00036e28
Node CRC 2771a666 != calculated CRC 14440ce0 for node at 00037554
Node CRC 270fa666 != calculated CRC 8df1f32c for node at 00037ce0
Node CRC 270ea666 != calculated CRC d639ca66 for node at 00038568
Node CRC 271fa666 != calculated CRC 56581f9a for node at 00038c44
Node CRC 271fa666 != calculated CRC 56581f9a for node at 00038c44
Node CRC 271fa666 != calculated CRC 56581f9a for node at 00038c44
Waiting for write to complete timed out in do_write_oneword.<5>Write of 68
bytes at 0x002fe
514 failed. returned -5, retlen 4
Node CRC f61f06e7 != calculated CRC fc464067 for node at 00038c44
Node CRC f61f06e7 != calculated CRC fc464067 for node at 00038c44
................................................................."
any advice?
thanks.
zhanghao
_________________________________________________________________
免费下载 MSN Explorer: http://explorer.msn.com/lccn
next reply other threads:[~2004-06-09 6:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 6:57 zhang hao [this message]
2004-06-09 9:41 ` jffs2 problem David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 8:29 JFFS2 problem Amit Kumar Sharma
2006-08-10 9:32 ` Artem B. Bityutskiy
2005-07-19 10:11 jffs2 problem Hinko Kocevar
2005-07-19 10:32 ` Artem B. Bityuckiy
2005-07-19 10:58 ` Hinko Kocevar
2005-07-19 11:05 ` Artem B. Bityuckiy
2005-07-19 11:45 ` Hinko Kocevar
2005-07-19 12:05 ` Artem B. Bityuckiy
2005-07-19 12:09 ` Steven Scholz
2005-07-19 12:21 ` Artem B. Bityuckiy
2005-07-19 12:19 ` Hinko Kocevar
2005-07-19 12:30 ` Hinko Kocevar
2004-03-22 16:18 JFFS2 problem Michael Palme
2003-07-30 2:37 Vikram Mehta
2002-07-11 13:29 JFFS2 Problem Frederic Giasson
2002-07-10 21:52 Snehaprabha
2002-07-11 7:05 ` David Woodhouse
2002-07-11 19:18 ` Snehaprabha
2002-07-11 19:32 ` Russ Dill
2001-09-03 8:49 jffs2 problem Wojciech Kromer
2001-04-30 22:03 JFFS2 Problem Jeff Smith
2001-05-03 21:55 ` David Woodhouse
2001-03-23 2:02 jffs2 problem Douglas S. J. De Couto
2001-03-23 8:37 ` David Woodhouse
2001-03-23 14:25 ` Douglas S. J. De Couto
2001-03-23 14:31 ` David Woodhouse
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=BAY13-F53EymQtczmul0003ee3c@hotmail.com \
--to=zh_chaohao@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox