memory.c:100: bad pmd

• Next message: Paul Menage: "Re: How to check the kernel compile options ?"
• Previous message: Richard B. Johnson: "Re: [PATCH] 2.5.4 Can't use spin_lock_* with wait_queue_head_t object."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I got these messages just a few minutes ago, while nothing else
interesting was happening. Hardware: Toshiba Satellite 2595CDS (it's a
Celeron, based on the 440BX and PIIX and all that), and my kernel is
2.4.17+O(1)k3+rmap12e. Dunno who this involves, or if it was just a
random thing, but I Cc'd rik considering that it's in mm/ and I've got
rmap in. :)

Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd 0000f3c1.
Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd 0000011e.
Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd 4023011c.
Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd 401b0fff.
Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd ffffffff.
Feb 12 15:54:19 localhost kernel: memory.c:100: bad pmd bffffb98.

I'll try to supply more info if it's needed, but as nothing locked up
(in fact, the system seems normal so far, I'm still sending my mail on
it), I don't have any backtrace info or anything like that.

• application/pgp-signature attachment: stored

-
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/

• Next message: Paul Menage: "Re: How to check the kernel compile options ?"
• Previous message: Richard B. Johnson: "Re: [PATCH] 2.5.4 Can't use spin_lock_* with wait_queue_head_t object."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:51 EST