All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Chris Webb <chris.webb@elastichosts.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: IO_PAGE_FAULT from SATA card during boot
Date: Tue, 8 Feb 2011 11:41:57 +0100	[thread overview]
Message-ID: <20110208104157.GU2106@amd.com> (raw)
In-Reply-To: <4D50A4B8.2070608@gmail.com>

On Mon, Feb 07, 2011 at 09:04:40PM -0500, Robert Hancock wrote:
> On 02/07/2011 11:48 AM, Chris Webb wrote:
> > I've now done this, swapping in a Highpoint R620. I get the same
> > IO_PAGE_FAULT, same timeouts on the sata card, but lspci now shows up the
> > device 03:00.1. I've put the new dmesg and lspci output at
> >
> >    http://cdw.me.uk/tmp/sata-fault-hpt.dmesg
> >    http://cdw.me.uk/tmp/sata-fault-hpt.lspci
> >
> > Again, problem is present both with 2.6.32.25 and 2.6.37.
> 
> Curious.. We don't even have a driver loaded for the PATA device on that 
> chip so I don't see how we could be telling it to do anything. As far as 
> I can see there are a few possible causes: Either the device is 
> generating read requests which appear to come from the PATA function 
> rather than the SATA one for some reason, the IOMMU is picking up the 
> wrong device function for requests from that device, or something in the 
> platform is somehow misconfiguring the device to cause this error. It 
> may not be easy to figure out which one is the cause, however.

The most likely reason for this is, that the add-on card uses both
request-ids (03:00.0 and 03:00.1) for requests originating from the SATA
controler. The address in the page-fault looks like an address the IOMMU
driver would assign but from a device which has no driver loaded.
If this is a know feature of the card the BIOS should detect it an
report it in the IVRS table with an alias-range. The driver would handle
it in this situation. Otherwise it looks like a problem with the
addon-card.

		Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2011-02-08 10:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 11:24 IO_PAGE_FAULT from SATA card during boot Chris Webb
2011-01-29 16:41 ` Robert Hancock
2011-01-30  1:54   ` Chris Webb
2011-01-30 15:37     ` Robert Hancock
2011-02-02 13:56       ` Chris Webb
2011-02-03  0:49         ` Robert Hancock
2011-02-03  8:56           ` Chris Webb
2011-02-07 17:48             ` Chris Webb
2011-02-08  2:04               ` Robert Hancock
2011-02-08 10:41                 ` Roedel, Joerg [this message]
2011-02-08 11:00                   ` Chris Webb
2011-02-08 14:43                     ` Robert Hancock
2011-02-08 14:48                       ` Chris Webb
2011-02-17  9:40                         ` Chris Webb
2011-02-18  0:22                           ` Robert Hancock
2011-02-21  9:39                             ` Roedel, Joerg

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=20110208104157.GU2106@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=chris.webb@elastichosts.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.