From: "Merger, Edgar [AUTOSOL/MAS/AUGS]" <Edgar.Merger@emerson.com>
To: Will Deacon <will@kernel.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: Joerg Roedel <jroedel@suse.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Kuehling, Felix" <Felix.Kuehling@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: RE: [EXTERNAL] Re: [PATCH] PCI: Mark AMD Raven iGPU ATS as broken
Date: Tue, 24 Nov 2020 05:32:12 +0000 [thread overview]
Message-ID: <MWHPR10MB1310DE70BAC5A86892D5398B89FB0@MWHPR10MB1310.namprd10.prod.outlook.com> (raw)
In-Reply-To: <20201123223356.GC12069@willie-the-truck>
This is a board developed by my company.
Subsystem-ID is ea50:0c19 or ea50:cc10 (depending on which particular carrier board the compute module is attached to), however we haven´t managed yet to enter this Subsystem-ID to every PCI-Device in the system, because of missing means to do that by our UEFI-FW. This might will change if we update to latest AGESA version.
-----Original Message-----
From: Will Deacon <will@kernel.org>
Sent: Montag, 23. November 2020 23:34
To: Deucher, Alexander <Alexander.Deucher@amd.com>
Cc: linux-kernel@vger.kernel.org; linux-pci@vger.kernel.org; iommu@lists.linux-foundation.org; Bjorn Helgaas <bhelgaas@google.com>; Merger, Edgar [AUTOSOL/MAS/AUGS] <Edgar.Merger@emerson.com>; Joerg Roedel <jroedel@suse.de>; Kuehling, Felix <Felix.Kuehling@amd.com>
Subject: [EXTERNAL] 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@kernel.org>
> > Sent: Monday, November 23, 2020 8:44 AM
> > To: linux-kernel@vger.kernel.org
> > Cc: linux-pci@vger.kernel.org; iommu@lists.linux-foundation.org;
> > Will Deacon <will@kernel.org>; Bjorn Helgaas <bhelgaas@google.com>;
> > Deucher, Alexander <Alexander.Deucher@amd.com>; Edgar Merger
> > <Edgar.Merger@emerson.com>; Joerg Roedel <jroedel@suse.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@google.com>
> > Cc: Alex Deucher <alexander.deucher@amd.com>
> > Reported-by: Edgar Merger <Edgar.Merger@emerson.com>
> > Suggested-by: Joerg Roedel <jroedel@suse.de>
> > Link:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Flore&d=DwIBAg&c=jOURTkCZzT8tVB5xPEYIm3YJGoxoTaQsQPzPKJGaWbo&r=BJxhacqqa4K1PJGm6_-862rdSP13_P6LVp7j_9l1xmg&m=WjiRGepDgI7voSyaAJcvnvZb6gsvZ1fvcnR2tm6bGXg&s=O1nU-RafBXMAS7Mao5Gtu6o1Xkuj8fg4oHQs74TssuA&e= .
> > 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@kernel.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://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_linux-2Diommu_MWHPR10MB1310CDB6829DDCF5EA84A14689150-40MWHPR10MB1310.namprd10.prod.outlook.com_&d=DwIBAg&c=jOURTkCZzT8tVB5xPEYIm3YJGoxoTaQsQPzPKJGaWbo&r=BJxhacqqa4K1PJGm6_-862rdSP13_P6LVp7j_9l1xmg&m=WjiRGepDgI7voSyaAJcvnvZb6gsvZ1fvcnR2tm6bGXg&s=9qyuCqHeOGaY1sKjkzNN5A6ks6PNF7V2M2PPckHyFKk&e=
is that this is a board developed by his company.
Edgar -- please can you answer Alex's questions?
Will
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-11-24 5:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 13:44 [PATCH] PCI: Mark AMD Raven iGPU ATS as broken Will Deacon
2020-11-23 21:04 ` Deucher, Alexander
2020-11-23 22:33 ` Will Deacon
2020-11-23 22:51 ` Felix Kuehling
2020-11-24 6:43 ` Huang Rui
2020-11-24 7:28 ` [EXTERNAL] " Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-24 15:05 ` Deucher, Alexander
2020-11-25 6:05 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-25 9:16 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-25 10:03 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-25 16:07 ` Deucher, Alexander
2020-11-26 9:24 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-30 18:36 ` Deucher, Alexander
2020-12-07 4:53 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-12-08 8:23 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-12-09 7:59 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-12-09 14:23 ` Deucher, Alexander
2020-12-10 10:48 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-12-10 15:36 ` Deucher, Alexander
2020-12-10 16:25 ` Bjorn Helgaas
2020-11-24 5:32 ` Merger, Edgar [AUTOSOL/MAS/AUGS] [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR10MB1310DE70BAC5A86892D5398B89FB0@MWHPR10MB1310.namprd10.prod.outlook.com \
--to=edgar.merger@emerson.com \
--cc=Alexander.Deucher@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).