From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: All kernels after 2.6.32-git10 show only 1 CPU ** Fixed in 2.6.33-rc2 **
Date: Sun, 27 Dec 2009 23:55:36 +0000 [thread overview]
Message-ID: <4B37F3F8.5000108@blueyonder.co.uk> (raw)
In-Reply-To: <4B37F16D.1040000@blueyonder.co.uk>
On 27/12/09 23:44, Sid Boyce wrote:
> On 26/12/09 20:01, Len Brown wrote:
>> Sid,
>> If the kernel boots properly as of -rc2, then I would not worry
>> so much that it was broken at some point during the merge window.
>>
>> However, if it is still broken and you need to bisect back
>> into -merge to find out what caused it... note that
>> booting with "acpi=ht" may be a useful tool. For this
>> option will boot just enough of ACPI to enumerate processors,
>> but no more. (Of course if this option doesn't boot with
>> the previous working kernels, then alas, it will not be useful here)
>>
>> cheers,
>> Len Brown, Intel Open Source Technology Center
>>
>>
>>
>
> 2.6.32-git1 boots OK with 2 CPU's.
> 2.6.32-git2 boots with "acpi=ht" but only one CPU appears.
Without "acpi=ht" there is a solid lock up
"ALSA sound/pci/hda/hda_intel.c azx_get_response timeout, switching to
polling mode: last cmd=0x000f0000"
Regards
Sid.
> With 2.6.32-git2 booted
> # git bisect bad
> tindog:/usr/src/GIT/linux-git # git bisect good v2.6.32
> Bisecting: 4685 revisions left to test after this (roughly 12 steps)
> [f6c4c8195b5e7878823caa1181be404d9e86d369] Merge branch 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid
>
> This is where I lose understanding of what I've done as v2.6.32-git1 and
> -git2 are not accepted as valid revisions needed by git bisect.
> 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
next prev parent reply other threads:[~2009-12-27 23:55 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 [this message]
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
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=4B37F3F8.5000108@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.