Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751141AbWJRGL5 (ORCPT ); Wed, 18 Oct 2006 02:11:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751440AbWJRGL5 (ORCPT ); Wed, 18 Oct 2006 02:11:57 -0400 Received: from ozlabs.org ([203.10.76.45]:52629 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S1751141AbWJRGL4 (ORCPT ); Wed, 18 Oct 2006 02:11:56 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17717.50596.248553.816155@cargo.ozlabs.ibm.com> Date: Wed, 18 Oct 2006 16:11:48 +1000 From: Paul Mackerras To: Christoph Lameter Cc: Will Schmidt , akpm@osdl.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177! In-Reply-To: References: <1160764895.11239.14.camel@farscape> <1160769226.11239.22.camel@farscape> <1160773040.11239.28.camel@farscape> <1161026409.31903.15.camel@farscape> <1161031821.31903.28.camel@farscape> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1380 Lines: 38 Christoph, I also am hitting this BUG on a POWER5 partition. The relevant boot messages are: Zone PFN ranges: DMA 0 -> 524288 Normal 524288 -> 524288 early_node_map[3] active PFN ranges 1: 0 -> 32768 0: 32768 -> 278528 1: 278528 -> 524288 [boot]0015 Setup Done Built 2 zonelists. Total pages: 513760 Kernel command line: root=/dev/sdc3 [snip] freeing bootmem node 0 freeing bootmem node 1 Memory: 2046852k/2097152k available (5512k kernel code, 65056k reserved, 2204k data, 554k bss, 256k init) kernel BUG in __cache_alloc_node at /home/paulus/kernel/powerpc/mm/slab.c:3177! Since this is a virtualized system there is every possibility that the memory we get won't be divided into nodes in the nice neat manner you seem to be expecting. It just depends on what memory the hypervisor has free, and on what nodes, when the partition is booted. In other words, the assumption that node pfn ranges won't overlap is completely untenable for us. Linus' tree is currently broken for us. Any suggestions for how to fix it, since I am not very familiar with the NUMA code? Paul. - 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/