linux-kernel - Re: AHCI not working with VT-d enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4EA26C99.3080608@gmail.com>
Date:	Sat, 22 Oct 2011 01:11:21 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Tobias Geiger <tobias.geiger@...o.info>
CC:	linux-ide@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: AHCI not working with VT-d enabled

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/