linux-kernel - RE: Geode LX boot fails after x86 microcode revision change

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]

Message-ID: <F625F33982F5D847987879CC59FF132D6F5B@storexdag03.amd.com>
Date:	Tue, 8 Nov 2011 22:13:56 +0000
From:	"Petkov, Borislav" <Borislav.Petkov@....com>
To:	"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...64.org>
CC:	Daniel Drake <dsd@...top.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Geode LX boot fails after x86 microcode revision change

> On 11/08/2011 12:31 PM, Borislav Petkov wrote:
> >
> > it might be that the Geode doesn't have the patch level MSR.., can you
> > send /proc/cpuinfo from a working kernel please, say 3.1?
> >
> > Although, I have rdmsr_safe in the patch there so it actually shouldn't
> > be an issue, theoretically.
> >
> 
> rdmsr_safe() requires exception table support, may not be available yet.
> 
>        -hpa

This could definitely explain why it hangs, the rdmsr_safe call is
 in early_init_amd(), so it could really be too early for exception tables.

If so, then a family check is unavoidable.

Thanks.

(Please forgive the formatting, I'm using the xchange crap)



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