Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 7 Dec 2006 06:39:01 +0100 | From | Willy Tarreau <> | Subject | Re: vmscan.c:196: bad pmd (kernel 2.4.25) |
| |
Hi,
On Wed, Dec 06, 2006 at 09:22:29AM +0100, Jesper Juhl wrote: > The following messages just showed up in dmesg on one of my servers. > The server seems to be running fine but I would like to know if > there's a real problem here or if the message is just noise. > > The server is running 2.4.25 > > vmscan.c:196: bad pmd 000001e3. > vmscan.c:196: bad pmd 004001e3. ... > vmscan.c:196: bad pmd 378001e3. > vmscan.c:196: bad pmd 37c001e3.
I may be wrong, but to me it looks either like memory corruption affecting one pgd, and by extension all of its pmds, or an old bug in 2.4.25, but I don't recall seeing such a thing.
Anyway, I would personally reboot the server after such a thing, as I really don't like it when VM is going mad.
Regards, Willy
- 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/
| ![\](/images/icornerr.gif) |