Re: x86-64 bad pmds in 2.6.11.6 II

[Chris Wright <chrisw@osdl.org>]

* Andi Kleen (ak@suse.de) wrote:
> On Tue, May 10, 2005 at 12:59:38PM -0400, Dave Jones wrote:
> > On Tue, May 10, 2005 at 06:46:49PM +0200, Andi Kleen wrote:
> >  > On Tue, May 10, 2005 at 12:38:51PM -0400, Dave Jones wrote:
> >  > > On Tue, May 10, 2005 at 05:36:54AM -0400, Christopher Warner wrote:
> >  > >  > 2.6.11.5 kernel,
> >  > >  > Tyan S2882/dual AMD 246 opterons
> >  > >  > sh:18983: mm/memory.c:99: bad pmd ffff810005974cc8(00007ffffffffe46). 
> >  > >  > sh:18983: mm/memory.c:99: bad pmd ffff810005974cd0(00007ffffffffe47).
> >  > > 
> >  > > That's the 3rd or 4th time I've seen this reported on this hardware.
> >  > > It's not exclusive to it, but it does seem more susceptible
> >  > > for some reason. Spooky.
> >  > 
> >  > It seems to be clear now that it is hardware independent.
> >  > 
> >  > I actually got it once now too, but only after 24+h stress test :/
> >  > 
> >  > I have a better debugging patch now that I will be testing soon,
> >  > hopefully that turns something up.
> > 
> > Ok, I'm respinning the Fedora update kernel today for other
> > reasons, if you have that patch in time, I'll toss it in too.
> 
> The patch has considerable overhead, probably not  good idea
> for a production rpm.

I don't mind running it here.  I've triggered it once, and not hit the
WARN_ON(start == end).  Current was "sh", not that helpful.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/