https://bugzilla.kernel.org/show_bug.cgi?id=220767

jslee ([email protected]) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #10 from jslee ([email protected]) ---
Same conflict on GIGABYTE X870E AORUS XTREME AI TOP (BIOS F13a/F13c, kernel
7.0.0-30):
pci 0000:00:02.1: bridge window [mem 0xdc400000-0xddafffff]: can't claim;
address conflict with AMDIF031:00 [mem 0xdd500000-0xdd500fff]
after which one of the two onboard AQC113C NICs gets "can't assign; no space",
and which one loses changes between boots.

Working, reversible workaround, no kernel patch:
https://github.com/jsleetw/fix_GIGABYTE_aitop_x870e

The AMDIF031 instance inside the bridge window is the second Promontory21
chipset's GPIO (\_SB.PCI0.GPP7.UP00.DP40.UP00.DP68.SPTO, _UID 2). Its _STA is
gated by a firmware variable in the same scope (SPTS). A 114-byte SSDT appended
via the initrd table upgrade clears that variable at load time, so SPTO._STA
returns 0, the platform device is never created, and the 00:02.1 window is
claimed exactly as the BIOS laid it out. Both NICs come up on every boot; the
only thing lost is the second chipset's 24 GPIO lines, which have no consumer
(the ASMP device that references them is itself gated off). Verified with
acpi_configfs at runtime and across cold boots.

The repo has a script to locate the device/variable on other boards
(scripts/find-chipset-gpio.sh) since the ASRock tables may name things
differently, plus a fix for a follow-on udev naming race once both NICs are
present. Caveat: kernel lockdown (Secure Boot) refuses initrd ACPI tables
silently.

For the record: GIGABYTE support answered that the board only supports Windows
11. The Oct 2025 LKML quirk for AMDIF031 ("kernel: resource: Add conditional
handling for ACPI device") was NAKed, so this seems to be the practical path
until the AMD reference ACPI code is changed.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to