From: enrico.scholz@sigma-chemnitz.de (Enrico Scholz)
To: linux-mtd@lists.infradead.org
Subject: Kernel oops with an unclean unmounted filesystem
Date: Mon, 24 Feb 2003 13:37:55 +0100 [thread overview]
Message-ID: <lyu1etzwf0.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1045748089.2242.37.camel@passion.cambridge.redhat.com> (David Woodhouse's message of "20 Feb 2003 13:34:50 +0000")
David Woodhouse <dwmw2@infradead.org> writes:
>> What exactly did you do there ? I mean creating and/or
>> modifying. The problem is the node is written with valid
>> CRC, so it seems to be correct, but the node content is
>> totally crap. Compressed data size = 0x6b6b6b6b.
>
> That's slab poisoning...
>
> What other drivers are present in your system?
I am running a heavily patched 2.5.59 kernel (rmk + ported PXA +
specific architecture patches) with potentially broken hardware
(PXA250 B1 stepping) so it is possible that other parts of the
system are guilty.
But because the problem disappears with recent CVS version of
JFFS2 it is probably caused by it. Since it is fixed in CVS I do
not know if it is worth to trace it further; when you give me
patches adding additional debugging checks I can try to get the
necessary information.
> Can you reproduce this?
Yes; 100% when doing a 'touch foobar' on the original 2.5.59
kernel (JFFS2 is not touched by my patches).
Thanks for your explainations
Enrico
prev parent reply other threads:[~2003-02-24 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 12:35 Kernel oops with an unclean unmounted filesystem Enrico Scholz
2003-02-19 14:42 ` Thomas Gleixner
2003-02-19 20:22 ` Thomas Gleixner
2003-02-19 20:18 ` Enrico Scholz
2003-02-20 11:48 ` Thomas Gleixner
2003-02-24 12:21 ` Enrico Scholz
2003-02-20 13:34 ` David Woodhouse
2003-02-24 12:37 ` Enrico Scholz [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=lyu1etzwf0.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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