From: Dave Jones <davej@redhat.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Bob Tracy <rct@gherkin.frus.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 12:30:00 -0400 [thread overview]
Message-ID: <20070516163000.GE30166@redhat.com> (raw)
In-Reply-To: <464B28F2.9050400@redhat.com>
On Wed, May 16, 2007 at 11:53:22AM -0400, Chuck Ebbert wrote:
> Bob Tracy wrote:
> > Jan Engelhardt wrote:
> >>> On Tue, 15 May 2007 22:13:14 -0500 (CDT) Bob Tracy wrote:
> >>>
> >>>> The 2.6.22-rc1 boot panics early in amd_mcheck_init() with my k6-III/450.
>
> > Intel machine check architecture supported.
> > general protection fault: 0000 [#1]
> > PREEMPT
> > Modules linked in:
> > CPU: 0
> > EIP: 0060:[<c01079f4>] Not tainted VLI
> > EFLAGS: 00010286 (2.6.22-rc1 #1)
> > EIP is at amd_mcheck_init+0x2b/0xc3
> >
>
> rdmsr with ecx == 0x179 (Machine Check Global Capabilities Register)
>
> Probably K6 doesn't have that.
sounds right. Intel style MCE capability was introduced with the Athlon
on AMD systems iirc.
> Caused by:
>
> [PATCH] i386: check capability
Though this would imply that Bobs K6-3 is reporting that it does have
that bit in its cpuid flags.
Bob, can you send your /proc/cpuinfo and dmesg |grep CPU ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-05-16 16:30 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 [this message]
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
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=20070516163000.GE30166@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