Christoph Lameter writes: > Could you confirm that there is indeed no memory on node 0? There is about a gigabyte of memory on node 0. > The expectation to have memory available on the node that you > bootstrap on is not unrealistic. 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. 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? Paul. - 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/
- Follow-Ups:
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- References:
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Will Schmidt <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Will Schmidt <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Paul Mackerras <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Paul Mackerras <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Paul Mackerras <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Anton Blanchard <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- Prev by Date: Re: [PATCH 1/7] KVM: userspace interface
- Next by Date: [PATCH] Use time_after instead of comparisons for jiffies (TAKE 2)
- Previous by thread: Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- Next by thread: Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
- Index(es):