Skip to contentSkip to conversation

x86-64 bad pmds in 2.6.11.6

DISCUSSION Clem Taylor 1 participant 1 message Apr 8, 2005

lore
Share & tools
lore
#0 lore raw

Dave Jones reported seeing bad pmd messages in 2.6.11.6. I've been seeing them with 2.6.11 and today with 2.6.11.6. When I first saw the problem I ran memtest86 and it didn't catch anything after ~3hours. However, I don't see them when X starts. They tend to happen after a program segfaults:

2.6.11:

Apr  3 23:23:33 klaatu kernel: sh[16361]: segfault at 0000000000000000
rip 0000000000000000 rsp 00007ffffffff020 error 14
Apr  3 23:23:33 klaatu kernel: mm/memory.c:97: bad pmd

ffff810027171010(00000000006b68b9).
.. many more ...

2.6.11.6:

Apr  8 12:03:17 klaatu kernel: grep[20971]: segfault at
0000000000000000 rip 0000000000000000 rsp 00007ffffffff090 error 14
Apr  8 12:03:17 klaatu kernel: mm/memory.c:97: bad pmd
ffff810095929010(0000000000000015).
.... many more ...
Apr  8 12:03:18 klaatu kernel: mm/memory.c:97: bad pmd
ffff8100959299d0(000034365f363878).
Apr  8 12:03:18 klaatu kernel: grep[21116]: segfault at
0000000000000000 rip 0000000000000000 rsp 00007ffffffff0a0 error 14
Apr  8 12:03:18 klaatu kernel: mm/memory.c:97: bad pmd

ffff810095f5b000(000000000000000f).
...

At the time I was doing a
find ... -exec grep -H ...
over a linux kernel tree.

I repeated the find and I didn't see segfaults the second run.

                                --Clem