[AMD Public Use] > -----Original Message----- > From: Will Deacon <will@xxxxxxxxxx> > Sent: Monday, November 23, 2020 8:44 AM > To: linux-kernel@xxxxxxxxxxxxxxx > Cc: linux-pci@xxxxxxxxxxxxxxx; iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; Will > Deacon <will@xxxxxxxxxx>; Bjorn Helgaas <bhelgaas@xxxxxxxxxx>; > Deucher, Alexander <Alexander.Deucher@xxxxxxx>; Edgar Merger > <Edgar.Merger@xxxxxxxxxxx>; Joerg Roedel <jroedel@xxxxxxx> > Subject: [PATCH] PCI: Mark AMD Raven iGPU ATS as broken > > Edgar Merger reports that the AMD Raven GPU does not work reliably on his > system when the IOMMU is enabled: > > | [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, > signaled seq=1, emitted seq=3 > | [...] > | amdgpu 0000:0b:00.0: GPU reset begin! > | AMD-Vi: Completion-Wait loop timed out > | iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT > device=0b:00.0 address=0x38edc0970] > > This is indicative of a hardware/platform configuration issue so, since > disabling ATS has been shown to resolve the problem, add a quirk to match > this particular device while Edgar follows-up with AMD for more information. > > Cc: Bjorn Helgaas <bhelgaas@xxxxxxxxxx> > Cc: Alex Deucher <alexander.deucher@xxxxxxx> > Reported-by: Edgar Merger <Edgar.Merger@xxxxxxxxxxx> > Suggested-by: Joerg Roedel <jroedel@xxxxxxx> > Link: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore. > kernel.org%2Flinux- > iommu%2FMWHPR10MB1310F042A30661D4158520B589FC0%40MWHPR10M > B1310.namprd10.prod.outlook.com&data=04%7C01%7Calexander.deuc > her%40amd.com%7C1a883fe14d0c408e7d9508d88fb5df4e%7C3dd8961fe488 > 4e608e11a82d994e183d%7C0%7C0%7C637417358593629699%7CUnknown%7 > CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi > LCJXVCI6Mn0%3D%7C1000&sdata=TMgKldWzsX8XZ0l7q3%2BszDWXQJJ > LOUfX5oGaoLN8n%2B8%3D&reserved=0 > Signed-off-by: Will Deacon <will@xxxxxxxxxx> > --- > > Hi all, > > Since Joerg is away at the moment, I'm posting this to try to make some > progress with the thread in the Link: tag. + Felix What system is this? Can you provide more details? Does a sbios update fix this? Disabling ATS for all Ravens will break GPU compute for a lot of people. I'd prefer to just black list this particular system (e.g., just SSIDs or revision) if possible. Alex > > Cheers, > > Will > > drivers/pci/quirks.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index > f70692ac79c5..3911b0ec57ba 100644 > --- a/drivers/pci/quirks.c > +++ b/drivers/pci/quirks.c > @@ -5176,6 +5176,8 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, > 0x6900, quirk_amd_harvest_no_ats); > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x7312, > quirk_amd_harvest_no_ats); > /* AMD Navi14 dGPU */ > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x7340, > quirk_amd_harvest_no_ats); > +/* AMD Raven platform iGPU */ > +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x15d8, > +quirk_amd_harvest_no_ats); > #endif /* CONFIG_PCI_ATS */ > > /* Freescale PCIe doesn't support MSI in RC mode */ > -- > 2.29.2.454.gaff20da3a2-goog
