From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse To: Konstantin Kletschke In-Reply-To: <20041120145020.GA15782@synertronixx3> References: <20041118163528.GA9471@synertronixx3> <1100959034.8600.33.camel@localhost.localdomain> <20041120145020.GA15782@synertronixx3> Content-Type: text/plain Date: Sat, 20 Nov 2004 15:12:44 +0000 Message-Id: <1100963565.7949.2.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: linux-mtd@lists.infradead.org Subject: Re: jffs2 Oops on 2.6.10-rc2 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2004-11-20 at 15:50 +0100, Konstantin Kletschke wrote: > >>EIP; c00b1c74 <===== > Code; c00b1c71 > d: e3 ff jecxz e <_EIP+0xe> > Code; c00b1c73 <===== > f: eb 00 jmp 11 <_EIP+0x11> <===== > Code; c00b1c75 > 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