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

[Christoph Lameter <clameter@sgi.com>]

On Fri, 20 Oct 2006, Paul Mackerras wrote:

> What exactly does "available" mean in this context?  The console log I
> posted earlier showed node 0 as having an active PFN range of 32768 -
> 278528 (245760 pages, or 960MB), and then showed a "freeing bootmem
> node 0" message, *before* we hit the BUG.

Available in the sense that the page allocator can allocate from them. 
Will's console output shows that all memory of node 0 is allocated and not 
available.

> If "available" doesn't mean "there are active pages which have been
> given to the VM system via free_all_bootmem_node()", what does it
> mean?

The page allocator must be running and able to serve pages from the boot 
node. This fails for some reason and the slab cannot bootstrap. The memory 
not available is the first guess. Could you trace the allocation in the 
page allocator (__alloc_pages) when the slab attempts to bootstrap and 
figure out why exactly the allocation fails?


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