public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: dedekind@infradead.org
Cc: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Re: Kernel oops in jffs2 mount - any ideas?
Date: Tue, 14 Nov 2006 17:08:12 +1300	[thread overview]
Message-ID: <4559412C.8080102@tait.co.nz> (raw)
In-Reply-To: <1163411683.3925.31.camel@sauron>

Artem Bityutskiy wrote:

> So the crash is somewhere in the CFI code. You should try to dig it and
> realize why it oopses.

Pretty much at the same point except now its the garbage collector 
crashing and leaving a lock on an inode so the kernel stalls.

No clues as to what is going on though :-(

[   13.591311] jffs2_scan_eraseblock(): Node at 0x0004aff8 {0x1985, 
0xe001, 0x0000002d) has invalid CRC 0xd7218112 (calculated 0x05000000)
[   13.617310] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b000: 0xd721 instead
[   13.638175] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b010: 0x4558 instead
[   13.656489] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b014: 0x0502 instead
[   13.674599] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b018: 0xbf85 instead
[   13.692594] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b01c: 0x584a instead
[   13.710884] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b020: 0x7474 instead
[   13.728881] jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found 
at 0x0004b024: 0x31ff instead
[   15.178914] Oops: kernel access of bad area, sig: 11 [#1]
[   15.189159] NIP: C0113524 LR: C0114128 CTR: C0113524
[   15.199017] REGS: c3cafcd0 TRAP: 0300   Not tainted  (2.6.18-buildroot)
[   15.212119] MSR: 00009032 <EE,ME,IR,DR>  CR: 22008028  XER: 0000005F
[   15.224743] DAR: FF80101B, DSISR: C0000000
[   15.232877] TASK = c036e410[280] 'jffs2_gcd_mtd1' THREAD: c3cae000
[   15.244778] GPR00: 00000000 C3CAFD80 C036E410 FF800FFF C3C2E678 
00000000 C0352A44 E67B3F7B
[   15.261366] GPR08: 000DF464 C01AF99C FF800FFF C0113524 22008024 
00000000 C3CAFE38 00000000
[   15.277955] GPR16: C3CAFE24 C01C0000 C3CAFDA8 00000000 C3CAFE28 
C3C2E640 C0352A20 00000000
[   15.294544] GPR24: 000DF464 C3C2E640 00000028 00000000 000DF464 
C3C2E678 C03FEC14 C3C2E678
[   15.311479] NIP [C0113524] put_chip+0xa0/0x2e8
[   15.320294] LR [C0114128] cfi_intelext_read+0x1a0/0x240
[   15.330656] Call Trace:
[   15.335509] [C3CAFD80] [C3C2E640] 0xc3c2e640 (unreliable)
[   15.346223] [C3CAFDA0] [C0114128] cfi_intelext_read+0x1a0/0x240
[   15.357974] [C3CAFDF0] [C010C8A0] part_read+0x84/0xe0
[   15.367997] [C3CAFE10] [C00B6AD4] 
jffs2_do_read_inode_internal+0x12c/0x1124
[   15.381821] [C3CAFE90] [C00B7B30] jffs2_do_crccheck_inode+0x64/0xc0
[   15.394262] [C3CAFF00] [C00BBF9C] jffs2_garbage_collect_pass+0x194/0x8a4
[   15.407568] [C3CAFF50] [C00BDE04] jffs2_garbage_collect_thread+0xa8/0x178
[   15.421046] [C3CAFFF0] [C000514C] kernel_thread+0x44/0x60
[   15.431745] Instruction dump:
[   15.437622] 3863a000 4beffdf5 387f001c 38800003 38a00001 38c00000 
4befb5d5 80010024
[   15.453000] 83e1001c 38210020 7c0803a6 4e800020 <800a001c> 2f800000 
419effd0 7d435378
[   15.470060] VFS: Mounted root (jffs2 filesystem).
[   15.479675] Freeing unused kernel memory: 92k init
[   15.488661] jffs2_lookup()
[   15.493994] jffs2_read_inode(): inode->i_ino == 3
[   15.503383] [JFFS2 DBG] (1) jffs2_do_read_inode: read inode #3
[   15.514963] [JFFS2 DBG] (1) jffs2_do_read_inode_internal: ino #3 
nlink is 1
[   15.528803] [JFFS2 DBG] (1) jffs2_get_inode_nodes: ino #3
[   15.539699] [JFFS2 DBG] (1) jffs2_get_inode_nodes: read 40 bytes at 
0x04b868(2).
[   15.554222] [JFFS2 DBG] (1) jffs2_alloc_full_dirent: c3ca4ee0
[   15.565732] [JFFS2 DBG] (1) jffs2_add_fd_to_list: add dirent "zero", 
ino #166
[   15.579790] [JFFS2 DBG] (1) jffs2_get_inode_nodes: read 40 bytes at 
0x04b7f0(2).
[   15.594479] [JFFS2 DBG] (1) jffs2_alloc_full_dirent: c3ca4fe0
[   15.605904] [JFFS2 DBG] (1) jffs2_add_fd_to_list: add dirent 
"urandom", ino #165
[   15.620569] [JFFS2 DBG] (1) jffs2_get_inode_nodes: read 40 bytes at 
0x04b778(2).
[   15.635260] [JFFS2 DBG] (1) jffs2_alloc_full_dirent: c3ca43e0
[   15.646848] [JFFS2 DBG] (1) jffs2_add_fd_to_list: add dirent "ttyp9", 
ino #164
[   15.661007] [JFFS2 DBG] (1) jffs2_get_inode_nodes: read 40 bytes at 
0x04b700(2).
[   15.675722] [JFFS2 DBG] (1) jffs2_alloc_full_dirent: c3ca4760
...
...
...
[   20.078514] jffs2_read_inode(): inode->i_ino == 12
[   20.087997] [JFFS2 DBG] (1) jffs2_do_read_inode: read inode #12
[   20.099752] [JFFS2 DBG] (1) jffs2_do_read_inode: waiting for ino #12 
in state 1

HELP!

-- 
Robin



=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

  parent reply	other threads:[~2006-11-14  4:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  0:24 Kernel oops in jffs2 mount - any ideas? Robin Gilks
2006-11-10  8:09 ` Artem Bityutskiy
2006-11-13  3:24   ` Robin Gilks
2006-11-13  9:54     ` Artem Bityutskiy
2006-11-13 23:00       ` Robin Gilks
2006-11-14  4:08       ` Robin Gilks [this message]
2006-11-14  7:59         ` Joakim Tjernlund
2006-11-14 21:17           ` Robin Gilks
2006-11-14 22:59           ` Robin Gilks
2006-11-14 19:46         ` Carlos Munoz

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=4559412C.8080102@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --cc=dedekind@infradead.org \
    --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