* Christoph Lameter <clameter@sgi.com> wrote:

quoted text
> On Tue, 15 Apr 2008, Ingo Molnar wrote:
> 
> > and the bug pattern seems to be memory corruption - not memory 
> > exhaustion.
> 
> SLUB does not do a memory allocation where it fails here but simply 
> accesses per cpu information that is expected to be already zeroed.
> 
> > i.e. we allocated RAM but it got corrupted after allocation.
> 
> In some situations we are screwing up the per cpu data handling on 32 
> bit x86? Adding Mike. This looks like the per cpu area overlaps with 
> something else?

yep, that was my other theory - and i doubled CONFIG_NR_CPUS to reduce 
that chance.

in hindsight ... that wont save us from any overlap, right?

what's the best way to artificially increase the size of the allocated 
per cpu area? (say double it)

	Ingo
--
unsubscribe notice
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/