public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: Borislav Petkov <bp@amd64.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 3.2-rcX regression: boot failure on AMD K6-III/450
Date: Mon, 28 Nov 2011 08:47:38 -0600	[thread overview]
Message-ID: <20111128144738.GA3119@gherkin.frus.com> (raw)
In-Reply-To: <20111128140143.GA4522@x1.osrc.amd.com>

On Mon, Nov 28, 2011 at 03:01:43PM +0100, Borislav Petkov wrote:
> can you try the following patch:
> (...)
> bcb80e53877c ("x86, microcode, AMD: Add microcode revision to
> /proc/cpuinfo") added support for dumping microcode patch level in
> /proc/cpuinfo on AMD. Although we were very cautious and did rdmsr_safe
> the microcode patch level MSR, this broke booting on Geode LX because
> this CPU doesn't have that MSR and at the time we do the read, exception
> tables which are used by rdmsr_safe are not yet initialized, leading to
> the boot hang.
> 
> This is the simple fix which enables the microcode line in /proc/cpuinfo
> for K8 and newer (it is not that interesting for older boxes anyway :-)).
> 
> Reported-and-bisected-and-tested-by: Daniel Drake <dsd@laptop.org>
> Link: http://lkml.kernel.org/r/CAMLZHHTSuHZoPbm_YfB8G05JA+xKCE4+Jmj4NW8mnZUHogQSBA@mail.gmail.com
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>

That fixed it.  Thank you!

--Bob

  reply	other threads:[~2011-11-28 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 18:17 [BUG] 3.2-rcX regression: boot failure on AMD K6-III/450 Bob Tracy
2011-11-28 14:01 ` Borislav Petkov
2011-11-28 14:47   ` Bob Tracy [this message]
2011-11-28 15:36     ` Borislav Petkov

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=20111128144738.GA3119@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=bp@amd64.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox