Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758484AbYCZQa0 (ORCPT ); Wed, 26 Mar 2008 12:30:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753325AbYCZQaQ (ORCPT ); Wed, 26 Mar 2008 12:30:16 -0400 Received: from relay1.sgi.com ([192.48.171.29]:41076 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752625AbYCZQaP (ORCPT ); Wed, 26 Mar 2008 12:30:15 -0400 Date: Wed, 26 Mar 2008 09:28:16 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Daniel Yeisley cc: Pekka Enberg , akpm@linux-foundation.org, mel@csn.ul.ie, olaf@aepfle.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH] slab: fix cache_cache bootstrap in kmem_cache_init() In-Reply-To: <1206535048.7468.4.camel@localhost.localdomain> Message-ID: References: <47E9EB77.9060909@cs.helsinki.fi> <1206535048.7468.4.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 19 On Wed, 26 Mar 2008, Daniel Yeisley wrote: > The only way I could get the ES7000 to boot with 2.6.24.x was with > memoryless nodes (or numa=off). The list corruption I saw was due to > CPU 0 not being on node 0. What is the ES7000? > I do see problems with memoryless nodes on 2.6.25-rc. I'll post a patch > for that shortly. Another patch in addition to the one we are discussing? Or another revision of the patch? -- 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/