linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* JFFS2 BUG ?
@ 2008-08-19 14:23 Jesse Malone
  2008-08-19 14:42 ` Jesse Malone
  2008-08-19 15:06 ` Jesse Malone
  0 siblings, 2 replies; 4+ messages in thread
From: Jesse Malone @ 2008-08-19 14:23 UTC (permalink / raw)
  To: linux-mtd

Hello,

I've been seeing jffs2 kernel oopses in kernel 2.6.25.10 (also in earlier
kernels, specifically 2.5.24.3). Here's the oops:

JFFS2 error: (309) jffs2_get_inode_nodes: can .
------------[ cut here ]------------
kernel BUG at fs/jffs2/readinode.c:542!
Oops: Kernel BUG, sig: 9 [#1]
FRAME_POINTER chip: 0x01f:0x1e82 rev 2
Modules linked in:
PC is at jffs2_free_tmp_dnode_info_list+0x44/0x54
LR is at 0x0
pc : [<900aa384>]    lr : [<00000000>]    Not tainted
sp : 91dc1e04  r12: 901e72e8  r11: 9024ee00
r10: 91d70e20  r9 : 91d70e20  r8 : 00000012
r7 : 91dc1e04  r6 : 91d70e00  r5 : 91dc1e70  r4 : 00000000
r3 : 91cf4000  r2 : 91d70e00  r1 : 91da842c  r0 : 00570cb4
Flags: qvnzC
Mode bits: hjmde....g
CPU Mode: Supervisor
Process: jffs2_gcd_mtd3 [309] (task: 91c17600 thread: 91dc0000)
Stack: (0x91dc1e04 to 0x91dc2000)
1e00:          900ab378 91dc1e40 00570ab4 00000037 00000000 00000000 91dc1e70
1e20: 91d3b600 91d3b200 0000008c fffffffb 00000151 91da8420 00000420 00000000
1e40: 900ab3dc 91dc1e94 91dc1e70 91dc1eb8 00000000 91d3b200 91d3b600 900b0560
1e60: 91d3b200 00000000 91dc2f18 00000000 91d11ac0 00000000 000008cb 00000000
1e80: 00000000 00000000 00000000 91dc1eac 901fe690 900abd36 91dc1efc 91d3b600
1ea0: 91d2f9f0 00000000 91d3b200 91d3b200 900b0560 91d3b200 901fe690 00000000
1ec0: ffffe000 91dc0000 91c1774c 91d3b200 90019b6a 91dc1ee4 901fe660 91c17628
1ee0: 00000000 9017abe6 91dc1f10 901fe660 91c17600 00000000 ffffe000 900af3e4
1f00: 91dc1f38 91d2f9f0 91d3b22c 00000000 00000001 91d3b200 900b0560 91d3b200
1f20: 900247b0 91dc1f34 91dc0000 91d3b200 00000000 9001f146 900b0642 91dc1fdc
1f40: 91dc0000 91d3b200 00000000 ffffe000 91dc0000 900b0560 91d3b200 007707d7
1f60: 007707d8 007707d9 007707da 007707db 007707dc 007707dd 007707de 007707df
1f80: 007707e0 007707e1 007707e2 007707e3 90000 00000000 00000000 00000000
9002
Call trace:
 [<900ab378>] jffs2_get_inode_nodes+0xd3c/0xd7c
 [<900ab3dc>] jffs2_do_read_inode_internal+0x24/0x7d8
 [<900abd36>] jffs2_do_crccheck_inode+0x3a/0x70
 [<900af3e4>] jffs2_garbage_collect_pass+0x138/0x52c
 [<900b0642>] jffs2_garbage_collect_thread+0xe2/0x108
 [<90020058>] do_exit+0x0/0x438


What do you make of this?

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: JFFS2 BUG ?
  2008-08-19 14:23 JFFS2 BUG ? Jesse Malone
@ 2008-08-19 14:42 ` Jesse Malone
  2008-08-19 15:06 ` Jesse Malone
  1 sibling, 0 replies; 4+ messages in thread
From: Jesse Malone @ 2008-08-19 14:42 UTC (permalink / raw)
  To: jmalone; +Cc: linux-mtd

...sorry that earlier version was 2.6.24.3


AUTHOR wrote Jesse Malone
> Hello,
>
> I've been seeing jffs2 kernel oopses in kernel 2.6.25.10 (also in earlier
> kernels, specifically 2.5.24.3). Here's the oops:
>
> JFFS2 error: (309) jffs2_get_inode_nodes: can .
> ------------[ cut here ]------------
> kernel BUG at fs/jffs2/readinode.c:542!
> Oops: Kernel BUG, sig: 9 [#1]
> FRAME_POINTER chip: 0x01f:0x1e82 rev 2
> Modules linked in:
> PC is at jffs2_free_tmp_dnode_info_list+0x44/0x54
> LR is at 0x0
> pc : [<900aa384>]    lr : [<00000000>]    Not tainted
> sp : 91dc1e04  r12: 901e72e8  r11: 9024ee00
> r10: 91d70e20  r9 : 91d70e20  r8 : 00000012
> r7 : 91dc1e04  r6 : 91d70e00  r5 : 91dc1e70  r4 : 00000000
> r3 : 91cf4000  r2 : 91d70e00  r1 : 91da842c  r0 : 00570cb4
> Flags: qvnzC
> Mode bits: hjmde....g
> CPU Mode: Supervisor
> Process: jffs2_gcd_mtd3 [309] (task: 91c17600 thread: 91dc0000)
> Stack: (0x91dc1e04 to 0x91dc2000)
> 1e00:          900ab378 91dc1e40 00570ab4 00000037 00000000 00000000
> 91dc1e70
> 1e20: 91d3b600 91d3b200 0000008c fffffffb 00000151 91da8420 00000420
> 00000000
> 1e40: 900ab3dc 91dc1e94 91dc1e70 91dc1eb8 00000000 91d3b200 91d3b600
> 900b0560
> 1e60: 91d3b200 00000000 91dc2f18 00000000 91d11ac0 00000000 000008cb
> 00000000
> 1e80: 00000000 00000000 00000000 91dc1eac 901fe690 900abd36 91dc1efc
> 91d3b600
> 1ea0: 91d2f9f0 00000000 91d3b200 91d3b200 900b0560 91d3b200 901fe690
> 00000000
> 1ec0: ffffe000 91dc0000 91c1774c 91d3b200 90019b6a 91dc1ee4 901fe660
> 91c17628
> 1ee0: 00000000 9017abe6 91dc1f10 901fe660 91c17600 00000000 ffffe000
> 900af3e4
> 1f00: 91dc1f38 91d2f9f0 91d3b22c 00000000 00000001 91d3b200 900b0560
> 91d3b200
> 1f20: 900247b0 91dc1f34 91dc0000 91d3b200 00000000 9001f146 900b0642
> 91dc1fdc
> 1f40: 91dc0000 91d3b200 00000000 ffffe000 91dc0000 900b0560 91d3b200
> 007707d7
> 1f60: 007707d8 007707d9 007707da 007707db 007707dc 007707dd 007707de
> 007707df
> 1f80: 007707e0 007707e1 007707e2 007707e3 90000 00000000 00000000 00000000
> 9002
> Call trace:
>  [<900ab378>] jffs2_get_inode_nodes+0xd3c/0xd7c
>  [<900ab3dc>] jffs2_do_read_inode_internal+0x24/0x7d8
>  [<900abd36>] jffs2_do_crccheck_inode+0x3a/0x70
>  [<900af3e4>] jffs2_garbage_collect_pass+0x138/0x52c
>  [<900b0642>] jffs2_garbage_collect_thread+0xe2/0x108
>  [<90020058>] do_exit+0x0/0x438
>
>
> What do you make of this?
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: JFFS2 BUG ?
  2008-08-19 14:23 JFFS2 BUG ? Jesse Malone
  2008-08-19 14:42 ` Jesse Malone
@ 2008-08-19 15:06 ` Jesse Malone
  1 sibling, 0 replies; 4+ messages in thread
From: Jesse Malone @ 2008-08-19 15:06 UTC (permalink / raw)
  To: jmalone; +Cc: linux-mtd

I should mention that this is an atmel kernel, so actually
2.6.25.10.atmel.2. Sorry for the omission




AUTHOR wrote Jesse Malone
> Hello,
>
> I've been seeing jffs2 kernel oopses in kernel 2.6.25.10 (also in earlier
> kernels, specifically 2.5.24.3). Here's the oops:
>
> JFFS2 error: (309) jffs2_get_inode_nodes: can .
> ------------[ cut here ]------------
> kernel BUG at fs/jffs2/readinode.c:542!
> Oops: Kernel BUG, sig: 9 [#1]
> FRAME_POINTER chip: 0x01f:0x1e82 rev 2
> Modules linked in:
> PC is at jffs2_free_tmp_dnode_info_list+0x44/0x54
> LR is at 0x0
> pc : [<900aa384>]    lr : [<00000000>]    Not tainted
> sp : 91dc1e04  r12: 901e72e8  r11: 9024ee00
> r10: 91d70e20  r9 : 91d70e20  r8 : 00000012
> r7 : 91dc1e04  r6 : 91d70e00  r5 : 91dc1e70  r4 : 00000000
> r3 : 91cf4000  r2 : 91d70e00  r1 : 91da842c  r0 : 00570cb4
> Flags: qvnzC
> Mode bits: hjmde....g
> CPU Mode: Supervisor
> Process: jffs2_gcd_mtd3 [309] (task: 91c17600 thread: 91dc0000)
> Stack: (0x91dc1e04 to 0x91dc2000)
> 1e00:          900ab378 91dc1e40 00570ab4 00000037 00000000 00000000
> 91dc1e70
> 1e20: 91d3b600 91d3b200 0000008c fffffffb 00000151 91da8420 00000420
> 00000000
> 1e40: 900ab3dc 91dc1e94 91dc1e70 91dc1eb8 00000000 91d3b200 91d3b600
> 900b0560
> 1e60: 91d3b200 00000000 91dc2f18 00000000 91d11ac0 00000000 000008cb
> 00000000
> 1e80: 00000000 00000000 00000000 91dc1eac 901fe690 900abd36 91dc1efc
> 91d3b600
> 1ea0: 91d2f9f0 00000000 91d3b200 91d3b200 900b0560 91d3b200 901fe690
> 00000000
> 1ec0: ffffe000 91dc0000 91c1774c 91d3b200 90019b6a 91dc1ee4 901fe660
> 91c17628
> 1ee0: 00000000 9017abe6 91dc1f10 901fe660 91c17600 00000000 ffffe000
> 900af3e4
> 1f00: 91dc1f38 91d2f9f0 91d3b22c 00000000 00000001 91d3b200 900b0560
> 91d3b200
> 1f20: 900247b0 91dc1f34 91dc0000 91d3b200 00000000 9001f146 900b0642
> 91dc1fdc
> 1f40: 91dc0000 91d3b200 00000000 ffffe000 91dc0000 900b0560 91d3b200
> 007707d7
> 1f60: 007707d8 007707d9 007707da 007707db 007707dc 007707dd 007707de
> 007707df
> 1f80: 007707e0 007707e1 007707e2 007707e3 90000 00000000 00000000 00000000
> 9002
> Call trace:
>  [<900ab378>] jffs2_get_inode_nodes+0xd3c/0xd7c
>  [<900ab3dc>] jffs2_do_read_inode_internal+0x24/0x7d8
>  [<900abd36>] jffs2_do_crccheck_inode+0x3a/0x70
>  [<900af3e4>] jffs2_garbage_collect_pass+0x138/0x52c
>  [<900b0642>] jffs2_garbage_collect_thread+0xe2/0x108
>  [<90020058>] do_exit+0x0/0x438
>
>
> What do you make of this?
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread
* JFFS2 BUG()
@ 2009-05-18 13:58 Felix Radensky
  0 siblings, 0 replies; 4+ messages in thread
From: Felix Radensky @ 2009-05-18 13:58 UTC (permalink / raw)
  To: linux-mtd

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-05-18 15:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-18 13:58 JFFS2 BUG() Felix Radensky
  -- 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

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).