public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Tim Hockin <thockin@hockin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Opteron fatal machine check during PCI probe
Date: Thu, 17 Jun 2004 02:23:00 +0200	[thread overview]
Message-ID: <20040617022300.6ba744bb.ak@suse.de> (raw)
In-Reply-To: <20040617000602.GA7435@hockin.org>

On Wed, 16 Jun 2004 17:06:02 -0700
Tim Hockin <thockin@hockin.org> wrote:

> Hey all,
> 
> I have a couple dual Opteron boxen that consistently gets an MCE during
> PCI probing. This is from linux-2.6.6, but the EXACT same scenario happens
> on a 2.4.x kernel.

> The MCE shows that the error is an IO read, with the address 0xfdfc000cfe.
> The RIP points to pci_conf1_read(), when we try to inw() from the PCI data
> register.

Is it an master abort (0x100 set in MC4_STATUS) ?
If yes it's an BIOS issue, the BIOS are supposed to disable that one.

> This is called during the PCI probing, and stops the kernel dead in it's
> tracks.  The disassembly of the surrounding code is:
> 
> ffffffff802822c5:	89 ca                	mov    %ecx,%edx
> ffffffff802822c7:	83 e2 02             	and    $0x2,%edx
> ffffffff802822ca:	66 81 c2 fc 0c       	add    $0xcfc,%dx
> ffffffff802822cf:	66 ed                	in     (%dx),%ax
> 
> This all seems legit to me.
> 
> What is interesting is that the address 0xfdfc000cfe is correct in the
> low-order 16 bits.  The extra 0xfdfc000000 is what is puzzling to me, or
> maybe it's a red herring.

It is. in only uses 16 bits of its operand.


-Andi

      reply	other threads:[~2004-06-17  0:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  0:06 Opteron fatal machine check during PCI probe Tim Hockin
2004-06-17  0:23 ` Andi Kleen [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=20040617022300.6ba744bb.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@hockin.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