From: David Woodhouse <dwmw2@infradead.org>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 Oops on 2.6.10-rc2
Date: Sat, 20 Nov 2004 15:12:44 +0000 [thread overview]
Message-ID: <1100963565.7949.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20041120145020.GA15782@synertronixx3>
On Sat, 2004-11-20 at 15:50 +0100, Konstantin Kletschke wrote:
> >>EIP; c00b1c74 <jffs2_build_remove_unlinked_inode+30/ec> <=====
> Code; c00b1c71 <jffs2_build_remove_unlinked_inode+2d/ec>
> d: e3 ff jecxz e <_EIP+0xe>
> Code; c00b1c73 <jffs2_build_remove_unlinked_inode+2f/ec> <=====
> f: eb 00 jmp 11 <_EIP+0x11> <=====
> Code; c00b1c75 <jffs2_build_remove_unlinked_inode+31/ec>
> 11: 40 inc %eax
Would be nice to see the actual code at jffs2_b_r_u_i+0x30, which isn't
in the above. Can you show the output of 'objdump -d' for the function
in question? And/or the result of telling gdb 'list *0xc00b1c74' on your
vmlinux?
It would also be useful to see the output with CONFIG_JFFS2_FS_DEBUG=1
when mounting the offending file system.
--
dwmw2
prev parent reply other threads:[~2004-11-20 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 16:35 jffs2 Oops on 2.6.10-rc2 Konstantin Kletschke
2004-11-18 17:20 ` Konstantin Kletschke
2004-11-20 13:57 ` David Woodhouse
2004-11-20 14:47 ` David Woodhouse
2004-11-20 14:50 ` Konstantin Kletschke
2004-11-20 14:57 ` David Woodhouse
2004-11-20 15:13 ` Artem B. Bityuckiy
2004-11-20 16:28 ` Konstantin Kletschke
2004-11-20 16:31 ` Konstantin Kletschke
2004-11-20 16:35 ` Konstantin Kletschke
2004-11-20 16:34 ` David Woodhouse
2004-11-22 10:27 ` Ian Campbell
2004-11-22 10:50 ` Ian Campbell
2004-11-22 11:05 ` David Woodhouse
2004-11-22 11:42 ` Ian Campbell
2004-11-20 15:12 ` David Woodhouse [this message]
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=1100963565.7949.2.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lists@ku-gbr.de \
/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