linux-kernel - Re: only a single core (out of 8) initialized

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 05 Jun 2009 19:24:58 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	david@...g.hm
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: only a single core (out of 8) initialized

david@...g.hm wrote:
> On Thu, 4 Jun 2009, Andrew Morton wrote:
> 
>> Subject: Re: only a single core (out of 8) initialized
>>
>> On Thu, 4 Jun 2009 19:52:36 -0700 (PDT) david@...g.hm wrote:
>>
>>> this is 2.6.30-rc7
>>
>> Were any earlier kernels OK?
>>
>>>  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?
> 
> this is actually the newer of the two systems. I've already escalated up 
> to Tyan about the fact that this board won't see the Intel SSD drives 
> (unless you hotplug the drive). I've forwarded this to them as well. 
> their website does show a newer bios than what was shipped to me.

Yeah, it seems like a BIOS problem on that system. It's missing a bunch 
of the ACPI tables that the other system has.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/