[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B3A6AF4.7040907@blueyonder.co.uk>
Date: Tue, 29 Dec 2009 20:47:48 +0000
From: Sid Boyce <sboyce@...eyonder.co.uk>
To: Len Brown <lenb@...nel.org>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
x86@...nel.org
Subject: Re: All kernels after 2.6.32-git10 show only 1 CPU ** NOT Fixed
in 2.6.33-rc2 either **
On 29/12/09 20:19, Len Brown wrote:
> On Mon, 28 Dec 2009, Sid Boyce wrote:
>
>> This dmesg is from a freshly built 2.6.32. The following do not appear
>> in later 2.6.32-git or 2.6.33-rc kernels.
>> # grep LAPIC /DMESG_2.6.32_tindog
>> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
>> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
>> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
>> ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]
>
> Right, your local apic is not found, ie this is missing
> in the 2.6.33 dmesg:
>
> ACPI: Local APIC address 0xfee00000
>
> Strange, as CONFIG_X86_LOCAL_APIC=y
>
> -Len
> Len Brown, Intel Open Source Technology Center
>
That is the case for >2.6.32-git1. As I could get some early 2.6.32-git
kernels to boot, I didn't spot the difference until I started to compare
the dmesg outputs lately.
I checked the BIOS and it's the latest available.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
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/
Powered by blists - more mailing lists