x86-64 bad pmds in 2.6.11.6
Quoted 10 lines · Dave Jones
Quoted 9 lines · Andi Kleen
Quoted 2 lines · Dave Jones
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.?Quoted 4 lines
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).
Quoted 8 lines
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.
Hi, Dave, all --
Does anyone remember if they saw any system instability at the time of these messages ?
I'm running 2.6.11 on an SMP Opteron box, which is exhibiting these notices. The box occasionally then behaves like it would during a serious memory leak - the load average shoots up, the box becomes unresponsive, stops accepting network connections, (but memory resources are not entirely starved, and nor does the kernel kill any processes off.)
Then - a few minutes later, the computer returns to normal. This seems to happen maybe twice a week. Thankfully, it's not ruined my weekend with a phone call from support yet, but it might. ;-)
If you do remember instability at this time, which was cured with an upgrade, then I will schedule some down time to try this out.
Signature · 2 lines
Regards, Andy Davidson [email protected] Systems Administrator, Ebuyer (UK) Ltd