On Thu, Mar 31, 2005 at 12:41:17PM +0200, Andi Kleen wrote:
> On Wed, Mar 30, 2005 at 04:44:55PM -0500, Dave Jones wrote:
> > [apologies to Andi for getting this twice, I goofed the l-k address
> > the first time]
> >
> >
> > I arrived at the office today to find my workstation had this spew
> > in its dmesg buffer..
>
> Looks like random memory corruption to me.
>
> Can you enable slab debugging etc.?
>
> > mm/memory.c:97: bad pmd ffff81004b017438(00000038a5500a88).
> > mm/memory.c:97: bad pmd ffff81004b017440(0000000000000003).
> > mm/memory.c:97: bad pmd ffff81004b017448(00007ffffffff73b).
> > mm/memory.c:97: bad pmd ffff81004b017450(00007ffffffff73c).
> > etc..
I realised today that this happens every time X starts up for
the first time. I did some experiments, and found that with 2.6.12rc1
it's gone. Either it got fixed accidentally, or its hidden now
by one of the many changes in 4-level patches.
I'll try and narrow this down a little more tomorrow, to see if I
can pinpoint the exact -bk snapshot (may be tricky given they were
broken for a while), as it'd be good to get this fixed in 2.6.11.x
if .12 isn't going to show up any time soon.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
