From: Linus Torvalds <torvalds@osdl.org>
To: "Georg C. F. Greve" <greve@fsfeurope.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Thu, 30 Dec 2004 14:23:01 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0412301418521.22893@ppc970.osdl.org> (raw)
In-Reply-To: <m3zmzvl9x1.fsf@reason.gnu-hamburg>
On Thu, 30 Dec 2004, Georg C. F. Greve wrote:
>
> lt> Any chance that you can get a full oops, with register info?
> lt> Right now your errors only have the call trace, not the registers
> lt> or the EIP itself..
>
> Yes, for the first two times, the top of the crash report scrolled off
> the screen and I don't have a serial console handy. The third crash
> contained the
>
> EFLAGS: 00010002 (2.6.10)
> EIP is at free_block+0x45/0xd0
> eax: 46484849 ebx: df2b1000 ecx: df2b1050 edx: df2ab000
> esi: c183cd80 edi: 00000001 ebp: 00000018 esp: c188fef8
> ds: 007b es: 007b ss: 0068
> Process events/0 (pid: 6, threadinfo:c188e000 task=c185ca20)
> Stack: c183cdb8 c1858810 c1858800 00000018 c183cd80 c0141724 c183cd80 c1858810
> 00000018 c183ccb8 c183cd80 00000002 c183cce0 c01417c6 c183cd80 c1858800
> 00000000 c183ccb8 c183ce10 00000003 c170fc20 c183b000 c170fc24 00000000
>
> header, which I think may contain what you were looking for.
Ok. This is apparently a slab cache corruption issue.
Can you compile with SLAB_DEBUG and DEBUG_PAGEALLOC turned on, since that
may well catch something in the act (or it may make the machine so
unusably slow that it's not funny - who knows..)
> Meanwhile, because of the trouble, I gave Alans patch-2.6.10-ac1 a try
> and again put ext3 on dm-crypt on raid5, and: No crash so far despite
> moving and removing ~100 gigabytes a couple of times on to/from the
> partition.
Goodie. Maybe Alan already knows what it's about. Alan? Any slab
corruption or wild pointers that you are aware of? However:
> I did however get occasional
>
> EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #37306376: directory entry across blocks - offset=0, inode=3350155169, rec_len=11148, name_len=1
I suspect that it's more of the slab corruption thing, and Alan's patch
ended up moving something around subtly enough that you don't get the
crash, but instead get corrupted buffer heads or similar.. Your BTTV
issues are interesting, though.
Linus
next prev parent reply other threads:[~2004-12-30 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:31 Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds [this message]
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King
2004-12-31 9:58 ` Georg C. F. Greve
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones
2004-12-30 10:21 Nick Warne
2004-12-31 11:46 Manfred Spraul
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=Pine.LNX.4.58.0412301418521.22893@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greve@fsfeurope.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®