On Thu, 2014-04-10 at 09:19 -0700, Davidlohr Bueso wrote:
> Attaching a dmesg from one of the kernels that boots. It doesn't appear
> to have much of the related information... is there any debug config
> option I can enable that might give you more data?
I'd like the contents of /sys/firmware/acpi/tables/DMAR please. And
please could you also apply this patch to both the last-working and
first-failing kernels and show me the output in both cases?
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index dd576c0..d52ac03 100644
--- a/drivers/iommu/intel-iommu.c
+++ b/drivers/iommu/intel-iommu.c
@@ -683,6 +683,12 @@ static struct intel_iommu *device_to_iommu(int segment, u8 bus, u8 devfn)
out:
rcu_read_unlock();
+ if (iommu)
+ printk("Device %x:%02x:%02x.%d on IOMMU at %llx\n", segment, bus,
+ PCI_SLOT(devfn), PCI_FUNC(devfn), drhd->reg_base_addr);
+ else
+ printk("Device %x:%02x:%02x.%d on no IOMMU\n", segment, bus,
+ PCI_SLOT(devfn), PCI_FUNC(devfn));
return iommu;
}
--
Sent with Evolution's ActiveSync support.
David Woodhouse Open Source Technology Centre
David.Woodhouse@xxxxxxxxx Intel Corporation
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
