On Fri Dec 06 19, Lu Baolu wrote:
[snip]
>
>Can you please try below change? Let's check whether the afending
>address has been mapped for device 01.00.2.
>
>$ git diff
>diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>index db7bfd4f2d20..d9daf66be849 100644
>--- a/drivers/iommu/iommu.c
>+++ b/drivers/iommu/iommu.c
>@@ -663,6 +663,8 @@ static int 
>iommu_group_create_direct_mappings(struct iommu_group *group,
>                        ret = iommu_map(domain, addr, addr, pg_size, 
>entry->prot);
>                        if (ret)
>                                goto out;
>+
>+                       dev_info(dev, "Setting identity map [0x%Lx - 
>0x%Lx] for group %d\n", addr, addr + pg_size, group->id);
>                }
>
>        }
>
>I am doubting that device 01.00.2 is not in the device scope of
>
>[    4.485108] DMAR: RMRR base: 0x000000bdf6f000 end: 0x000000bdf7efff
>
>By the way, does device 01.00.2 works well after binding the driver?
>

When I boot it with passthrough it doesn't get to a point where I can
login. I think the serial console on these systems is tied to the ilo,
so the conserver connection could be making things
worse. Unfortunately the system is remote. I should have more time now
to focus on debugging this.

Attaching console output for the above patch.

Regards,
Jerry

>Best regards,
>baolu
>