[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201123223356.GC12069@willie-the-truck>
Date: Mon, 23 Nov 2020 22:33:56 +0000
From: Will Deacon <will@...nel.org>
To: "Deucher, Alexander" <Alexander.Deucher@....com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Edgar Merger <Edgar.Merger@...rson.com>,
Joerg Roedel <jroedel@...e.de>,
"Kuehling, Felix" <Felix.Kuehling@....com>
Subject: Re: [PATCH] PCI: Mark AMD Raven iGPU ATS as broken
On Mon, Nov 23, 2020 at 09:04:14PM +0000, Deucher, Alexander wrote:
> [AMD Public Use]
>
> > -----Original Message-----
> > From: Will Deacon <will@...nel.org>
> > Sent: Monday, November 23, 2020 8:44 AM
> > To: linux-kernel@...r.kernel.org
> > Cc: linux-pci@...r.kernel.org; iommu@...ts.linux-foundation.org; Will
> > Deacon <will@...nel.org>; Bjorn Helgaas <bhelgaas@...gle.com>;
> > Deucher, Alexander <Alexander.Deucher@....com>; Edgar Merger
> > <Edgar.Merger@...rson.com>; Joerg Roedel <jroedel@...e.de>
> > 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@...gle.com>
> > Cc: Alex Deucher <alexander.deucher@....com>
> > Reported-by: Edgar Merger <Edgar.Merger@...rson.com>
> > Suggested-by: Joerg Roedel <jroedel@...e.de>
> > 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@...nel.org>
> > ---
> >
> > 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.
Cheers, Alex. I'll have to defer to Edgar for the details, as my
understanding from the original thread over at:
https://lore.kernel.org/linux-iommu/MWHPR10MB1310CDB6829DDCF5EA84A14689150@MWHPR10MB1310.namprd10.prod.outlook.com/
is that this is a board developed by his company.
Edgar -- please can you answer Alex's questions?
Will
Powered by blists - more mailing lists