Re: Is there some bug in ext3 in 2.4.25?

["Stephen C. Tweedie" <sct@redhat.com>]

Hi,

On Fri, 2004-04-02 at 11:20, Daniel Fenert wrote:

> >> This sounds like memory corruption (which could be caused by a misbehaving
> >> driver or by flaky hardware) because transaction->t_ilist is not used at
> >> all by the kernel code. Did this box run stable with other kernels?
> >
> >Sounds like bad memory to me.  The only other report of this I've seen
> >was at
> >
> >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115935
> >
> >and that machine didn't pass memtest86.
> 
> It passed memtest86, 6 or 7 hours, any further hints?

Well, 7 hours is often not enough for memtest86, I usually recommend 24
hours if there are signs of bad hardware.  But other than that, I can't
think of anything ext3-related --- ext3 simply doesn't ever set that
flag.  If it's being set, something is stomping on ext3's transaction
struct.  That _could_ be the kernel, but it could be just about anything
touching memory after it's freed; or it could be bad hardware.

What modules are you using?  Is there anything unusual in common between
your machine or its use and that in #115935?  

Rebuilding the kernel to enable slab debugging may well be useful if
there's something stomping on transaction structs.

Cheers,
 Stephen