* Re: [Bug 216252] New: AMD APU IOMMU: pci 0000:00:00.2: can't derive routing for PCI INT A
[not found] <bug-216252-41252@https.bugzilla.kernel.org/>
@ 2022-07-15 16:19 ` Bjorn Helgaas
0 siblings, 0 replies; only message in thread
From: Bjorn Helgaas @ 2022-07-15 16:19 UTC (permalink / raw)
To: linux-pci
Cc: Karri Hämäläinen, Joerg Roedel,
Suravee Suthikulpanit
[+cc Joerg, Suravee]
On Fri, Jul 15, 2022 at 02:21:17PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216252
>
> Bug ID: 216252
> Summary: AMD APU IOMMU: pci 0000:00:00.2: can't derive routing
> for PCI INT A
> Product: Platform Specific/Hardware
> Version: 2.5
> Kernel Version: 5.18.5
> Hardware: AMD
> Priority: P1
> Assignee: platform_x86_64@kernel-bugs.osdl.org
> Reporter: kh.bugreport@outlook.com
> CC: adm@prnet.info, bjorn@helgaas.com,
> bugzilla.kernel.org@e3q.eu,
> drivers_pci@kernel-bugs.osdl.org, hxss@ya.ru,
> josh.mcd31@gmail.com, kh.bugreport@outlook.com,
> marcel@ziswiler.com, snafu109@gmail.com,
> whenov@gmail.com
> Regression: No
>
> Created attachment 301439
> --> https://bugzilla.kernel.org/attachment.cgi?id=301439&action=edit
> acpidump from ASRock B450M Pro4-F R2.0
>
> +++ This bug was initially created as a clone of Bug #212261 +++
>
> Bug 212261 - pci 0000:00:00.2: can't derive routing for PCI INT A
> https://bugzilla.kernel.org/show_bug.cgi?id=212261
>
>
> Crossposting from drivers/pci to Platform Specific/Hardware/x86-64 with AMD
> hardware specificy.
>
> AMD IOMMU IRQ routing problems.
>
> [ 0.273902] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
> [ 0.273932] pci 0000:00:00.2: can't derive routing for PCI INT A
> [ 0.273933] pci 0000:00:00.2: PCI INT A: not connected
>
> Common to AMD reference ACPI / firmware / AGESA for Zen APUs?
> At least Raven Ridge (desktop) and Renoir (both desktop and laptop).
>
> Personally tested with AMD 2200G and 4650G with Asus and ASRock B450
> motherboards.
My guess is a BIOS bug, maybe missing _PRT entries.
Added a couple AMD IOMMU folks in case they've seen this or have BIOS
contacts who could help.
^ permalink raw reply [flat|nested] only message in thread