From: Borislav Petkov <bp@amd64.org>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Geode LX boot fails after x86 microcode revision change
Date: Tue, 8 Nov 2011 21:31:16 +0100 [thread overview]
Message-ID: <20111108203116.GF25083@aftab> (raw)
In-Reply-To: <CAMLZHHTSuHZoPbm_YfB8G05JA+xKCE4+Jmj4NW8mnZUHogQSBA@mail.gmail.com>
On Tue, Nov 08, 2011 at 01:59:40PM -0600, Daniel Drake wrote:
> Hi,
>
> Linux-3.1 works fine on OLPC XO-1 (Geode LX) but latest linus master
> fails to boot. It hangs so early on that we don't even receive any
> output over serial.
>
> git bisect tracked it down to:
>
>
> commit bcb80e53877c2045d9e52f4a71372c3fe6501f6f
> Author: Borislav Petkov <borislav.petkov@amd.com>
> Date: Mon Oct 17 16:34:36 2011 +0200
>
> x86, microcode, AMD: Add microcode revision to /proc/cpuinfo
>
> Enable microcode revision output for AMD after 506ed6b53e00 ("x86,
> intel: Output microcode revision in /proc/cpuinfo") did it for Intel.
>
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
>
>
> Any thoughts?
Hmm,
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.
Can you also install msr-tools and do
$ rdmsr 0x8b
as root on the working kernel? If it hangs there too, then we know why.
Also, can you boot if you comment out the rdmsr_safe line in
early_init_amd(), line 477:
// rdmsr_safe(MSR_AMD64_PATCH_LEVEL, &c->microcode, &dummy);
?
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2011-11-08 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 19:59 Geode LX boot fails after x86 microcode revision change Daniel Drake
2011-11-08 20:31 ` Borislav Petkov [this message]
2011-11-08 22:01 ` H. Peter Anvin
2011-11-08 22:13 ` Petkov, Borislav
2011-11-08 22:17 ` Daniel Drake
2011-11-08 22:37 ` Borislav Petkov
2011-11-08 22:59 ` Daniel Drake
2011-11-09 17:34 ` Borislav Petkov
2011-11-10 13:05 ` Srivatsa S. Bhat
2011-11-10 13:28 ` Borislav Petkov
2011-11-10 13:37 ` Srivatsa S. Bhat
2011-11-10 13:34 ` Srivatsa S. Bhat
2011-11-11 18:40 ` Daniel Drake
2011-11-12 13:50 ` Borislav Petkov
2011-11-08 22:19 ` H. Peter Anvin
2011-11-08 22:40 ` Borislav Petkov
2011-11-22 13:00 ` Borislav Petkov
2011-11-22 18:54 ` H. Peter Anvin
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=20111108203116.GF25083@aftab \
--to=bp@amd64.org \
--cc=dsd@laptop.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.