linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Tobias Geiger <tobias.geiger@vido.info>
Cc: linux-ide@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: AHCI not working with VT-d enabled
Date: Sat, 22 Oct 2011 01:11:21 -0600	[thread overview]
Message-ID: <4EA26C99.3080608@gmail.com> (raw)
In-Reply-To: <201110191404.27193.tobias.geiger@vido.info>

On 10/19/2011 06:04 AM, Tobias Geiger wrote:
> Hi,
>
> short description of my problem is:
> with vt-d enabled in bios the sata 6g ports are not recognized;
> when vt-d is disabled the sata6g ports work...
>
> Sata ports are on
> 04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9120 (rev 12)
>
> kernel is 3.1.0-rc8+
> Dmesg with vt-d enabled is here: http://pastebin.com/YLJU8yMJ
>
> Thanks for your input on this!
> Greetings
> Tobias

I think we've had another report about this. This is the error that's 
being hit:

[    1.056549] DRHD: handling fault status reg 2
[    1.056612] DMAR:[DMA Write] Request device [04:00.1] fault addr fffe0000
[    1.056614] DMAR:[fault reason 02] Present bit in context entry is clear

  Essentially it seems that this Marvell controller can produce PCIe 
transactions from the wrong device function (in this case presumably 
from the PATA part of the controller on function 1 instead of the AHCI 
part on function 0), and the IOMMU is blocking the access since the PATA 
function hasn't had any DMA mapping set up.

Not sure what we can do about this.. maybe some kind of PCI quirk for 
this device?

      reply	other threads:[~2011-10-22  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 12:04 AHCI not working with VT-d enabled Tobias Geiger
2011-10-22  7:11 ` 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=4EA26C99.3080608@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias.geiger@vido.info \
    /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;
as well as URLs for NNTP newsgroup(s).