From: "Joachim Deguara" <joachim.deguara@amd.com>
To: rct@gherkin.frus.com
Cc: "Andi Kleen" <ak@suse.de>, "Chuck Ebbert" <cebbert@redhat.com>,
"Jan Engelhardt" <jengelh@linux01.gwdg.de>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1
Date: Fri, 18 May 2007 16:38:27 +0200 [thread overview]
Message-ID: <200705181638.29657.joachim.deguara@amd.com> (raw)
In-Reply-To: <20070517233813.266B6DBA1@gherkin.frus.com>
On Friday 18 May 2007 01:38:13 rct@gherkin.frus.com wrote:
> Andi Kleen wrote:
> > Hmpf.
> >
> > We cold either use rdmsr_safe or add a family check again or clear it
> > in k6 setup. I think clearing it in setup is cleanest.
> >
> > Does this patch work?
> >
> > -Andi
> >
> > Clear MCE flag on AMD K6
> >
> > It reports machine check capability in CPUID, but doesn't actually
> > implement all the necessary MSRs of the standard Intel machine
> > check architecture.
> >
> > This fixes a boot failure recently introduced.
> >
> > Signed-off-by: Andi Kleen <ak@suse.de>
>
> ACK. I reinstalled Joachim's patch (default 2.6.22-rc1 state), and
> added your patch. Life is good: we have a fix/workaround.
Great, thanks for finding this and Andi for the patch. I'll talk to our labs
about dusting off old systems for testing ;)
-Joachim
prev parent reply other threads:[~2007-05-18 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 3:13 [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1 Bob Tracy
2007-05-16 4:27 ` Randy Dunlap
2007-05-16 7:03 ` Jan Engelhardt
2007-05-16 13:15 ` Bob Tracy
2007-05-16 15:53 ` Chuck Ebbert
2007-05-16 16:30 ` Dave Jones
2007-05-16 19:11 ` Bob Tracy
2007-05-16 19:22 ` Dave Jones
2007-05-16 21:07 ` Dave Jones
2007-05-17 4:36 ` Bob Tracy
2007-05-17 6:08 ` Dave Jones
2007-05-17 12:34 ` Bob Tracy
2007-05-17 12:35 ` Andi Kleen
2007-05-17 12:54 ` Bob Tracy
2007-05-17 23:38 ` Bob Tracy
2007-05-18 14:38 ` Joachim Deguara [this message]
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=200705181638.29657.joachim.deguara@amd.com \
--to=joachim.deguara@amd.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rct@gherkin.frus.com \
/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