From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 82761] DMAR:[fault reason 06] PTE Read access is not set
Date: Tue, 19 Aug 2014 21:55:11 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:46264 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1750939AbaHSVzP (ORCPT );
Tue, 19 Aug 2014 17:55:15 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 9ECED2015D
for ; Tue, 19 Aug 2014 21:55:14 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id 9AF2B20172
for ; Tue, 19 Aug 2014 21:55:12 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=82761
--- Comment #6 from Alex Williamson ---
Ok, then it's probably not a result of the PCIe-to-PCI bridge since 05:00.0 is
the correct requester ID for all the devices behind the bridge. Unfortunately
that means that the problem may not be fixable. We're only seeing reads to a
single address, which may mean the NIC is using that read to synchronize
transaction ordering, ex. using a DMA read to flush a DMA write from the
device. If the NIC driver has visibility of this address, then it could
attempt to do a coherent mapping for the device(s) to avoid the fault. If it
doesn't, then these NICs may simply be incompatible with the IOMMU.
Are these 3 separate NICs plugged into PCI slots on the motherboard or is this
a single triple-port card with embedded PCIe-to-PCI bridge?
You might be able to run the IOMMU in passthrough mode with iommu=pt
r8169.use_dac=1, but note the warning in modinfo "use_dac:Enable PCI DAC.
Unsafe on 32 bit PCI slot." Unfortunately if you don't enable use_dac, then
intel_iommu will ignore the passthrough option for these devices.
Also note that this problem has nothing to do with Virtualization/KVM.
Drivers/Network or perhaps Drivers/PCI would be a more appropriate
classification.
--
You are receiving this mail because:
You are watching the assignee of the bug.