All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Chris Webb <chris.webb@elastichosts.com>
Cc: linux-ide@vger.kernel.org, Joerg.Roedel@amd.com
Subject: Re: IO_PAGE_FAULT from SATA card during boot
Date: Mon, 07 Feb 2011 20:04:40 -0600	[thread overview]
Message-ID: <4D50A4B8.2070608@gmail.com> (raw)
In-Reply-To: <20110207174838.GA21124@arachsys.com>

On 02/07/2011 11:48 AM, Chris Webb wrote:
> Chris Webb<chris@arachsys.com>  writes:
>
>> Robert Hancock<hancockrwd@gmail.com>  writes:
>>
>>> Is it the same model of add-on card?
>>
>> Hi. Yes, they're four identical machines with four identical SATA
>> controllers.
>>
>>> This controller apparently has both a SATA and PATA controller on
>>> it. The PATA portion doesn't seem to be showing up in lspci, but
>>> obviously the BIOS saw some sign of it - and if the IOMMU reporting
>>> can be believed, it's trying to do a read request for some reason..
>>
>> Since SATA cards are cheap, I've ordered a different AHCI card to try
>> swapping out, so will be able to confirm if it's specific to this SATA card.
>
> 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.

Putting Joerg Roedel from AMD on the CC list to see if he has any more 
insight..

  reply	other threads:[~2011-02-08  2:04 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 [this message]
2011-02-08 10:41                 ` Roedel, Joerg
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=4D50A4B8.2070608@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=chris.webb@elastichosts.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.