public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Re: Kernel oops in jffs2 mount - any ideas?
Date: Wed, 15 Nov 2006 11:59:11 +1300	[thread overview]
Message-ID: <455A4A3F.4020304@tait.co.nz> (raw)
In-Reply-To: <4559775D.8030009@transmode.se>

Joakim Tjernlund wrote:
> Robin Gilks wrote:
>> 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 :-(
>>
>>
>> HELP!
>>
>>   
> You should apply the bug fix I sent the other day(Re: cfi_cmd0001.c
> broken w.r.t Erase Suspend solved, patch included).
> This closes nasty bug that I think should be applied to linus tree ASAP.
> 
>  Jocke

The plot thickens - I'm now getting the following crash at boot about 
60% of the time (the other 40% is as previously reported) - still not 
had a single successful boot!!).

[   14.528955] Oops: kernel access of bad area, sig: 11 [#1]
[   14.539250] NIP: C00B3494 LR: C00B9684 CTR: 00000000
[   14.549111] REGS: c0327a70 TRAP: 0300   Not tainted  (2.6.18-buildroot)
[   14.562213] MSR: 00009032 <EE,ME,IR,DR>  CR: 22002022  XER: 2000005F
[   14.574838] DAR: FF8010EB, DSISR: C0000000
[   14.582968] TASK = c0324b40[1] 'swapper' THREAD: c0326000
[   14.593316] GPR00: C00BA60C C0327B20 C0324B40 FF800FFF 00000139 
D81A5184 C0230000 00000000
[   14.609904] GPR08: C01AD0F0 000002A0 84511AD8 DA2B0DD8 82002022 
00000000 03FF9000 C01C0000
[   14.626494] GPR16: C3C9FF50 00000000 00000000 00000000 C3CA4395 
0000000A 000F3FD0 0000000F
[   14.643082] GPR24: 000F0000 00010000 C5183FD0 00000139 C5180000 
00000139 C3C01C00 000F3FD0
[   14.660018] NIP [C00B3494] jffs2_get_ino_cache+0x0/0x4c
[   14.670388] LR [C00B9684] jffs2_scan_make_ino_cache+0x1c/0xa8
[   14.681787] Call Trace:
[   14.686639] [C0327B20] [00010000] 0x10000 (unreliable)
[   14.696835] [C0327B40] [C00BA60C] jffs2_scan_medium+0xefc/0xfe4
[   14.708587] [C0327BC0] [C00BCA7C] jffs2_do_mount_fs+0x180/0x8ec
[   14.720337] [C0327BF0] [C00BEF0C] jffs2_do_fill_super+0xbc/0x244
[   14.732260] [C0327C10] [C00BF718] jffs2_get_sb_mtd+0xfc/0x19c
[   14.743665] [C0327C50] [C00BF9C4] jffs2_get_sb+0x180/0x228
[   14.754551] [C0327CE0] [C005A42C] vfs_kern_mount+0x5c/0xbc
[   14.765438] [C0327D00] [C005A4C8] do_kern_mount+0x3c/0x60
[   14.776151] [C0327D30] [C0072374] do_mount+0x394/0x680
[   14.786346] [C0327EB0] [C00729F8] sys_mount+0x98/0xe8
[   14.796369] [C0327EF0] [C021E864] do_mount_root+0x2c/0xc4
[   14.807082] [C0327F10] [C021E9C0] mount_block_root+0xc4/0x248
[   14.818487] [C0327F60] [C021EE3C] prepare_namespace+0xb8/0x190
[   14.830065] [C0327F80] [C0002494] init+0x254/0x2e4
[   14.839568] [C0327FF0] [C000514C] kernel_thread+0x44/0x60
[   14.850268] Instruction dump:
[   14.856145] 9421fff0 386300e4 38c00000 90010014 b0a4000a 38800003 
38a00001 4bf5b661
[   14.871523] 80010014 38210010 7c0803a6 4e800020 <816300ec> 548915fa 
7c69582e 2f030000
[   14.888894] Kernel panic - not syncing: Attempted to kill init!
[   14.900725]  <0>Rebooting in 1 seconds..



=======================================================================
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 22:59 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
2006-11-14  7:59         ` Joakim Tjernlund
2006-11-14 21:17           ` Robin Gilks
2006-11-14 22:59           ` Robin Gilks [this message]
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=455A4A3F.4020304@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --cc=Joakim.Tjernlund@transmode.se \
    --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