Hi!
On Wed, 2006-01-18 at 15:54 +0200, Pekka J Enberg wrote:
> Indeed that's because the kernel starts reclaiming memory and attempts to
> shrink the slabs. It's just that the page we're freeing is being managed
> by the slab allocator and I don't see how anyone else could be messing
> around with it. The fact that it's one bit error makes me think it could
> be due to faulty memory.
I have run memtest for 15 hours now, - no errors. Im running the kernel
with CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC enabled. Until now, no
more Bugs or Oopses occured.
I don't know if there's any way to reproduce the problem, but at least
I'll keep my eyes open.
Sven
--
Sven Lauritzen
--------------------------------------------------------------------
mailto:[email protected]
pub 1024D/95C9A892 sub 1024g/D30E490F ABCDEFGHIJKLM
Fp 2FA9 FC9B 078C 5BC7 87DC 0B0D 2329 94F6 95C9 A892 NOPQRSTUVWXYZ
--------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
