Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!

[Christoph Lameter]

On Thu, 19 Oct 2006, Paul Mackerras wrote:

> > Have memory available for slab boot strap on node 0? Or modify the boot 
> > code in such a way that it runs on node 1 or any other node that has 
> > memory available.
> 
> OK, then I don't understand.  There is about 1GB of memory on node 0,
> which is about half of the partition's memory, and it is even in a
> contiguous chunk, but it doesn't start at pfn 0:

And the memory is available? In some messages it showed that all of node 0 
memory was allocated on bootup! We end up in fallback_alloc which means 
that an allocation attempt failed to obtain memory. Could you figure out 
what exactly we are trying to allocate? Add some printk's? Why do we 
fallback?

> So it's not that node 0 doesn't have any pages.  Any other clues?

We are falling back. So something is going wrong. Either we request memory 
from an overallocated node or the page allocator for some other reason is 
not giving us the requested memory. If we figure out why then the fix is 
probably very simple.

I have no way of investigating the issue except by conjecture and code 
review since I have no ppc hardware.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/