[Bug 42679] New: DMA Read on Marvell 88SE9128 fails when Intel's IOMMU is on

Chris Wright chrisw at sous-sol.org
Mon Jan 30 23:32:11 UTC 2012

* Paweł Żak (pawel.zaq at gmail.com) wrote:
> On Mon, 30 Jan 2012 22:41:32 +0100, Don Dutile <ddutile at redhat.com> wrote:
> >Well, the lspci dump in the bugzilla report doesn't show a device
> >w/BDF=0b:00.1;
> >so, if the SATA device (which is 0b:00.0) is spitting out 0b:00.1
> >as the source
> >of any of its DMA packets, the IOMMU will fault on it, since
> >0b:00.1 didn't
> >request DMA mappings (0b:00.0 did).
> >I semi-recall someone else reporting this 'feature' on this list.
> >Wonder if pci-quirk has to filter this case (0b:00.0 on this system means
> >map for 0b:00.0 & 0b:00.1 -- ick!)
> >
> >do another lspci -vvv to ensure that 0b:00.1 wasn't excluded in the list.
> >if it doesn't exist, then the problem is the SATA device using an
> >unknown/unrecognized
> >BDF of 0b:00.1
> Yep, that's correct. I enabled all integrated peripherals on my
> motherboard and there were still no entries with BDF 0b:00.1 in
> lspci -vvv output. Should I take this problem to MSI then?

Yeah, something is not right.  Is there any BIOS control over that


More information about the iommu mailing list