[lkml]   [2006]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: vmscan.c:196: bad pmd (kernel 2.4.25)

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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-07 06:41    [W:0.025 / U:3.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site