From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@transmode.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 OOPS in 2.6.20
Date: Thu, 08 Mar 2007 18:37:27 +0000 [thread overview]
Message-ID: <1173379047.3461.482.camel@pmac.infradead.org> (raw)
In-Reply-To: <1173375879.26465.13.camel@gentoo-jocke.transmode.se>
On Thu, 2007-03-08 at 18:44 +0100, Joakim Tjernlund wrote:
> Got another board too that has an identical OOPS, but prints
> JFFS2 notice: (137) jffs2_get_inode_nodes: Node header CRC failed at 0x3aa87a0.
> {0040,4001,00000044,00000000}
> Just before the OOPS, here is the full OOPS:
> JFFS2 notice: (137) jffs2_get_inode_nodes: Node header CRC failed at 0x3aa87a0.
> {0040,4001,00000044,00000000}
> ------------[ cut here ]------------
> kernel BUG at fs/jffs2/readinode.c:376!
Can you make it print the flash offset of the offending node, and the
header contents (like the 0040,4001,00000044,00000000 above) before
dying? Then reproduce with CONFIG_JFFS2_FS_DEBUG=1 and show me the full
output.
--
dwmw2
next prev parent reply other threads:[~2007-03-08 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 17:14 JFFS2 OOPS in 2.6.20 Joakim Tjernlund
2007-03-08 17:33 ` Joakim Tjernlund
2007-03-08 17:44 ` Joakim Tjernlund
2007-03-08 18:37 ` David Woodhouse [this message]
2007-03-08 18:46 ` Artem Bityutskiy
2007-03-08 18:51 ` David Woodhouse
2007-03-09 9:02 ` Joakim Tjernlund
2007-03-09 9:23 ` David Woodhouse
2007-03-09 10:46 ` Joakim Tjernlund
2007-03-09 11:08 ` David Woodhouse
2007-03-09 11:15 ` Joakim Tjernlund
2007-03-09 11:24 ` David Woodhouse
2007-03-09 12:01 ` Joakim Tjernlund
2007-03-09 13:54 ` Joakim Tjernlund
2007-03-09 14:49 ` Joakim Tjernlund
2007-03-10 16:08 ` Joakim Tjernlund
2007-03-09 9:36 ` Joakim Tjernlund
2007-03-09 9:46 ` David Woodhouse
2007-03-09 10:56 ` Joakim Tjernlund
2007-03-09 13:11 ` Jörn Engel
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=1173379047.3461.482.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--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