From: Felix Radensky <felix@embedded-sol.com>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 BUG()
Date: Mon, 18 May 2009 16:58:46 +0300 [thread overview]
Message-ID: <4A116996.70403@embedded-sol.com> (raw)
Hi,
I've hit a BUG() in JFFS2 as described below. The JFSS2 partition
is 250MB on 1GB Samsung NAND flash. My kernel is 2.6.27,
running on AMCC 405EXr CPU (powerpc). The problem is not
easily reproducible. It is possible that partition was rather full when
BUG() was hit. Very similar problem was reported to the list a year
ago, but was not resolved, see
http://lists.infradead.org/pipermail/linux-mtd/2008-April/021454.html
Can the fix proposed by previous reporter solve the problem ?
I'm getting the following error message:
Data CRC 97eaebe7 != calculated CRC b76accbf for node at 07633a58
------------[ cut here ]------------
kernel BUG at fs/jffs2/file.c:251!
Oops: Exception in kernel mode, sig: 5 [#1]
Modules linked in: usbcore
NIP: c01086fc LR: c004ed24 CTR: c01086b0
REGS: df029c10 TRAP: 0700 Not tainted (2.6.27)
MSR: 00029030 <EE,ME,IR,DR> CR: 24442022 XER: 00000000
TASK = daafe490[5808] 'cp' THREAD: df028000
GPR00: 00000001 df029cc0 daafe490 dfb8cd00 c45ee4c8 00000000 00326000
00001000
GPR08: 00001000 cd822a00 00000004 00000004 27bba2e8 100586a0 00000000
00326000
GPR16: df029d0c df029d08 00000000 00000000 00001000 df029d10 dfb8cd00
cd822000
GPR24: 00000000 00326000 00001000 00000000 00000000 c45ee430 c0412160
00001000
NIP [c01086fc] jffs2_write_end+0x4c/0x2f4
LR [c004ed24] generic_file_buffered_write+0x190/0x650
Call Trace:
[df029cc0] [c01088d0] jffs2_write_end+0x220/0x2f4 (unreliable)
[df029d00] [c004ed24] generic_file_buffered_write+0x190/0x650
[df029d90] [c004f6e4] __generic_file_aio_write_nolock+0x23c/0x4a4
[df029e00] [c004f9b4] generic_file_aio_write+0x68/0xf8
[df029e30] [c00726cc] do_sync_write+0xc4/0x138
[df029ef0] [c0073134] vfs_write+0xb4/0x16c
[df029f10] [c0073664] sys_write+0x4c/0x90
[df029f40] [c000e11c] ret_from_syscall+0x0/0x3c
Instruction dump:
70090008 813d008c 54dc053e 38000000 82e9019c 7cd93378 7cb82b78 90010008
7f5c4214 41820004 7c000026 54001ffe <0f000000> 2f9a1000 3b600000 419e0008
---[ end trace 0b6b9614848c5573 ]---
Thanks a lot.
Felix.
next reply other threads:[~2009-05-18 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 13:58 Felix Radensky [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 14:23 JFFS2 BUG ? Jesse Malone
2008-08-19 14:42 ` Jesse Malone
2008-08-19 15:06 ` Jesse Malone
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=4A116996.70403@embedded-sol.com \
--to=felix@embedded-sol.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;
as well as URLs for NNTP newsgroup(s).