Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Jun 2002 17:05:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Jun 2002 17:05:39 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:65030 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Thu, 6 Jun 2002 17:05:33 -0400 Message-ID: <3CFFCE4B.F422EE7@zip.com.au> Date: Thu, 06 Jun 2002 14:04:11 -0700 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-pre8 i686) X-Accept-Language: en MIME-Version: 1.0 To: Andreas Dilger CC: Robert Love , "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: [patch] CONFIG_NR_CPUS In-Reply-To: <20020606.031520.08940800.davem@redhat.com> <1023377213.13787.2.camel@sinai> <3CFFBCA9.843C40F0@zip.com.au> <20020606205508.GN27817@turbolinux.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andreas Dilger wrote: > > On Jun 06, 2002 12:48 -0700, Andrew Morton wrote: > > But the arch maintainers should test one case please - x86 > > was locking up at boot on quad CPU with NR_CPUS=2. Others may do > > the same. > > Just a guess, but this could be because the two CPUs chosen for the > boot sequence are not physically numbered 0 and 1, so they are > overwriting the bounds of the per-CPU arrays. Well the code was assuming that the number of physical CPUs was always <= NR_CPUS unless max_cpus had been specified. I fixed that in 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/