From: Len Brown <lenb@kernel.org>
To: Sid Boyce <sboyce@blueyonder.co.uk>
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: Sat, 26 Dec 2009 15:01:31 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912261457550.4089@localhost.localdomain> (raw)
In-Reply-To: <4B363EEE.8020108@blueyonder.co.uk>
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
next prev parent reply other threads:[~2009-12-26 20:01 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 [this message]
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
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=alpine.LFD.2.00.0912261457550.4089@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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
all inboxes | Powered by JetHome®