From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by ozlabs.org (Postfix) with ESMTP id 07ACCDDF42 for ; Sat, 19 Jan 2008 09:19:57 +1100 (EST) Received: by fg-out-1718.google.com with SMTP id 16so1051476fgg.39 for ; Fri, 18 Jan 2008 14:19:55 -0800 (PST) Message-ID: <29495f1d0801181419q7ec24cc2v3843e5eba27fe207@mail.gmail.com> Date: Fri, 18 Jan 2008 14:19:54 -0800 From: "Nish Aravamudan" To: "Christoph Lameter" Subject: Re: crash in kmem_cache_init In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20080115150949.GA14089@aepfle.de> <84144f020801170414q7d408a74uf47a84b777c36a4a@mail.gmail.com> <20080117181222.GA24411@aepfle.de> <20080117211511.GA25320@aepfle.de> <20080118213011.GC10491@csn.ul.ie> Cc: lee.schermerhorn@hp.com, Olaf Hering , Linux MM , Mel Gorman , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Pekka Enberg , "Aneesh Kumar K.V" , hanth Aravamudan , KAMEZAWA Hiroyuki List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 1/18/08, Christoph Lameter wrote: > Could you try this patch? > > Memoryless nodes: Set N_NORMAL_MEMORY for a node if we do not support > HIGHMEM > > It seems that we only scan through zones to set N_NORMAL_MEMORY only if > CONFIG_HIGHMEM and CONFIG_NUMA are set. We need to set > N_NORMAL_MEMORY > in the !CONFIG_HIGHMEM case. I'm testing this exact patch right now on the machine Mel saw the issues with. Thanks, Nish