[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B37F3F8.5000108@blueyonder.co.uk>
Date: Sun, 27 Dec 2009 23:55:36 +0000
From: Sid Boyce <sboyce@...eyonder.co.uk>
To: Len Brown <lenb@...nel.org>
CC: linux-kernel@...r.kernel.org
Subject: Re: All kernels after 2.6.32-git10 show only 1 CPU ** Fixed in 2.6.33-rc2
**
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
--
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