Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752047AbWCBTdf (ORCPT ); Thu, 2 Mar 2006 14:33:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752048AbWCBTdf (ORCPT ); Thu, 2 Mar 2006 14:33:35 -0500 Received: from mx1.redhat.com ([66.187.233.31]:53963 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1752045AbWCBTde (ORCPT ); Thu, 2 Mar 2006 14:33:34 -0500 Date: Thu, 2 Mar 2006 14:31:29 -0500 From: Dave Jones To: "Brown, Len" Cc: Chuck Ebbert <76306.1226@compuserve.com>, linux-kernel , linux-acpi , Andi Kleen Subject: Re: 2.6.16rc5 'found' an extra CPU. Message-ID: <20060302193129.GA12498@redhat.com> Mail-Followup-To: Dave Jones , "Brown, Len" , Chuck Ebbert <76306.1226@compuserve.com>, linux-kernel , linux-acpi , Andi Kleen References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 813 Lines: 26 On Thu, Mar 02, 2006 at 02:26:24PM -0500, Brown, Len wrote: > Dave, > Your DSDT looks fine. > I was wrong assuming there were 3 Processor entries there. > > > > Did you really build a 256-CPU SMP kernel or is ACPI > > > ignoring CONFIG_NR_CPUS or something? > > > >Yes, it's =256. > > I expect this is the root problem. If this is the _cause_, something needs fixing, but it's hardly something we can brush off as 'the root problem'. It's entirely possible for such a configuration (higher CONFIG_NR_CPUS than actual cpus), cf. distro kernels. Dave - 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/