lkml.org 
[lkml]   [2006]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [BUG] at mm/slab.c:1235! (Version 2.6.15)
On Wed, 2006-01-18 at 14:22 +0200, Pekka Enberg wrote:
> > Try enabling CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC to see if
> > they pick up anything.

On Wed, 18 Jan 2006, Sven Lauritzen wrote:
> Ok, I'll try that. I guess I'll find the results in syslog?

Yes. They'll give us a better oops if they pick up something.

On Wed, 2006-01-18 at 14:22 +0200, Pekka Enberg wrote:
> > I don't quite see how this could happen. Is the box otherwise stable?
> > Have you run memtest86 on it?

On Wed, 18 Jan 2006, Sven Lauritzen wrote:
> It's the first crash within 4 days. I have exchanged motherboard and ram
> of the box, so maybe there's something worng. But it seems that the
> crash was caused by high traffic on the disk drive. 6:25 is the time,
> when findutils and logrotate and so on start to run.

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.

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

\
 
 \ /
  Last update: 2006-01-18 14:57    [W:0.779 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site