public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Len Brown <lenb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Re: All kernels after 2.6.32-git10  show only 1 CPU ** NOT Fixed in 2.6.33-rc2 either **
Date: Mon, 04 Jan 2010 17:23:50 +0000	[thread overview]
Message-ID: <4B422426.7090901@blueyonder.co.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0912291512380.14938@localhost.localdomain>

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
> 
> 

2.6.33-rc2-git5 booted and showed both CPU's on first boot, on
subsequent boots it hung at HDA irq 22 as it did on earlier kernels.
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


  parent reply	other threads:[~2010-01-04 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 16:55 All kernels after 2.6.32-git10 show only 1 CPU Sid Boyce
2009-12-24 13:05 ` Sid Boyce
2009-12-25  1:11   ` All kernels after 2.6.32-git10 show only 1 CPU ** Fixed in 2.6.33-rc2 ** Sid Boyce
2009-12-26 16:50     ` Sid Boyce
2009-12-26 20:01       ` Len Brown
2009-12-27 23:44         ` Sid Boyce
2009-12-27 23:55           ` Sid Boyce
2009-12-28 14:41             ` All kernels after 2.6.32-git10 show only 1 CPU ** NOT Fixed in 2.6.33-rc2 either ** Sid Boyce
2009-12-28 23:18               ` Sid Boyce
2009-12-29 20:19                 ` Len Brown
2009-12-29 20:47                   ` Sid Boyce
2010-01-04 17:23                   ` Sid Boyce [this message]
2009-12-25  7:38 ` All kernels after 2.6.32-git10 show only 1 CPU Yinghai Lu
2009-12-25 18:33   ` Sid Boyce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B422426.7090901@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox