linux-kernel - Re: Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 19 Jan 2009 14:07:36 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
CC:	Avuton Olrich <avuton@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due
 to dc1e35c

Suresh Siddha wrote:
> On Mon, Jan 19, 2009 at 01:46:37PM -0800, Avuton Olrich wrote:
>> On Mon, Jan 19, 2009 at 12:11 PM, Suresh Siddha
>> <suresh.b.siddha@...el.com> wrote:
>>> Avuton, Does your bios has an option which says limit the cpuid
>>> vector limit to '2' or something. Can you disable that option and
>>> re-check? It will typically be located under cpu configuration settings.
>> You're the winner of the prize. The culprit in my bios was:
>>
>> Max CPUID Value Limit: Enabled
> 
> Though the bios is the culprit and this option will severely limit
> the cpu capabilities that OS can take advantage of, OS should fallback
> to a safer mode. I will have a patch for it.
> 
> Also, I wonder, if we should complain/scream during boot if we find only
> fewer cpuid levels on modern generation cpu's.
> 

We should, or if this block is reversible, we should probably just undo 
it (the reason people put this block in places is because of, ahem, 
inferior operating systems having bugs.)

Do you know how this is managed?  Via an MSR?

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