linux-kernel - Re: All kernels after 2.6.32-git10 show only 1 CPU ** Fixed in 2.6.33-rc2 **

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.0912261457550.4089@localhost.localdomain>
Date:	Sat, 26 Dec 2009 15:01:31 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Sid Boyce <sboyce@...eyonder.co.uk>
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 **

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

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