Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751302AbZFEQsS (ORCPT ); Fri, 5 Jun 2009 12:48:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752328AbZFEQsC (ORCPT ); Fri, 5 Jun 2009 12:48:02 -0400 Received: from mail.lang.hm ([64.81.33.126]:40972 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751988AbZFEQsB (ORCPT ); Fri, 5 Jun 2009 12:48:01 -0400 Date: Fri, 5 Jun 2009 09:47:37 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard To: Andrew Morton cc: linux-kernel , linux-acpi@vger.kernel.org, Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" Subject: Re: only a single core (out of 8) initialized In-Reply-To: <20090604202933.d7c24c3d.akpm@linux-foundation.org> Message-ID: References: <20090604202933.d7c24c3d.akpm@linux-foundation.org> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1479 Lines: 51 On Thu, 4 Jun 2009, Andrew Morton wrote: > On Thu, 4 Jun 2009 19:52:36 -0700 (PDT) david@lang.hm wrote: > >> this is 2.6.30-rc7 > > Were any earlier kernels OK? sorry, I missed this question. I was running 2.6.29.1 when I noticed this problem. I haven't tried older kernels yet. David Lang >> with a patch added to debug a nv sata driver >> incompatibility with the Intel SSDs on a tyan motherboard >> >> on one system it sees all 8 cores, on the other system it only initializes >> one core. >> >> can anyone help me spot what's going wrong in the one that's only seeing a >> single core? If I'm reading things correctly it's seeing both sockets for >> the NUMA setup, but then only initializing one core on the first socket. > > good: > SMP: Allowing 8 CPUs, 4 hotplug CPUs > > bad: > SMP: Allowing 1 CPUs, 0 hotplug CPUs > > perhaps due to > ACPI: No APIC-table, disabling MPS > > You could have a poke around in arch/x86/kernel/smpboot.c() and find > out what happened here. I'd be suspecting this code triggered: > > /* no processor from mptable or madt */ > if (!num_processors) > num_processors = 1; > > because ACPI doesn't like that board. > > Did you look into updating the BIOS? > > -- 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/