All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: George Spelvin <linux@horizon.com>
Cc: tj@kernel.org, linux-ide@vger.kernel.org
Subject: Re: 88SE9172 additional PCI ID: 1b4b:9172
Date: Wed, 29 May 2013 22:41:22 -0600	[thread overview]
Message-ID: <51A6D872.2090100@gmail.com> (raw)
In-Reply-To: <20130528071220.3601.qmail@science.horizon.com>

On 05/28/2013 01:12 AM, George Spelvin wrote:
>> I don't think it's a typo.
>
> Indeed, pci.ids has three entries.
>
>> And we'll need a separate entry
>>
>>> (If I enable VT-d and the IOMMU, the devices are recognized but not the
>>> disks plugged into them, but I'm still working on figuring that out.)
>>
>> when the device gets working.
>
> I don't quite understand this.  With VT-d disabled in the BIOS,
> the devices *are* working.  I even have a port multiplier plugged
> into one.  (Which gets all confused by hdparm -m16, but whatever.)
>
> When I get time, I'm going to play with various BIOS and kernel
> options to narrow down the problem.  But that's for later.
>
> Can you explain what you think is not working now?

There are some known problems with some Marvell controllers and VT-d, 
apparently they issue PCIe requests containing the wrong device function 
causing IOMMU faults to occur. I believe a PCI quirk to work around the 
problem was either being worked on or finished - if it's in already, it 
might need this device ID added to it as well.

      parent reply	other threads:[~2013-05-30  4:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 23:31 88SE9172 additional PCI ID: 1b4b:9172 George Spelvin
2013-05-28  0:22 ` Tejun Heo
2013-05-28  7:12   ` George Spelvin
2013-05-28 22:31     ` Tejun Heo
2013-05-28 23:32       ` [PATCH] Use observed PCI ID for Marvell 88se9172 SATA controller George Spelvin
2013-05-29  1:22         ` [PATCH] ahci: add an " Tejun Heo
2013-05-29 12:36           ` George Spelvin
2013-05-30  6:52             ` Tejun Heo
2013-05-30  4:41     ` Robert Hancock [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=51A6D872.2090100@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=tj@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.