From: Dave Jones <davej@redhat.com>
To: Bob Tracy <rct@gherkin.frus.com>,
Chuck Ebbert <cebbert@redhat.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Joachim Deguara <joachim.deguara@amd.com>
Subject: Re: [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1
Date: Wed, 16 May 2007 17:07:16 -0400 [thread overview]
Message-ID: <20070516210716.GB16810@redhat.com> (raw)
In-Reply-To: <20070516192248.GA16810@redhat.com>
On Wed, May 16, 2007 at 03:22:48PM -0400, Dave Jones wrote:
> On Wed, May 16, 2007 at 02:11:56PM -0500, Bob Tracy wrote:
>
> > flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
> > bogomips : 902.78
> > clflush size : 32
>
> Ah so it really does think it has mce.
> I just dug out the datasheet for the K6-3, and true enough, it did have MCE, however,
> it isn't intel compatible. It has two MSRs (MCAR at 0x0, and MCTR at 0x01).
> Then the punchline..
>
> "Because the processor does not support machine check exceptions, the contents of the
> MCAR and MCTR are only affected by the WRMSR instruction and by RESET being sampled
> asserted (where all bits in each register are reset to 0)."
>
> In short, it's useless.
> We could clear the capability bit and pretend it isn't there, at no loss of
> functionality, or we could revert back to doing model checks instead of cpuid flag checks.
Bob, does this patch make it boot again for you?
Dave
Some AMD K6's advertise machine check capability, but don't actually
have an Intel compatible implementation. It also doesn't actually work,
so don't advertise it as being present.
Signed-off-by: Dave Jones <davej@redhat.com>
diff --git a/arch/i386/kernel/cpu/amd.c b/arch/i386/kernel/cpu/amd.c
index 4fec702..3a75c5b 100644
--- a/arch/i386/kernel/cpu/amd.c
+++ b/arch/i386/kernel/cpu/amd.c
@@ -197,7 +197,14 @@ static void __cpuinit init_amd(struct cpuinfo_x86 *c)
/* placeholder for any needed mods */
break;
}
+
+ /*
+ * Some K6's advertise MCE, but it's incompatible
+ * to Intel style MCE, and also non-functional.
+ */
+ clear_bit(X86_FEATURE_MCE, c->x86_capability);
break;
+
case 6: /* An Athlon/Duron */
/* Bit 15 of Athlon specific MSR 15, needs to be 0
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-05-16 21:08 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 [this message]
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
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=20070516210716.GB16810@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=joachim.deguara@amd.com \
--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