http://bugzilla.opensuse.org/show_bug.cgi?id=1190854 http://bugzilla.opensuse.org/show_bug.cgi?id=1190854#c2 --- Comment #2 from Hadrien Grasland <grasland@lal.in2p3.fr> --- Cross-checking the dmesg logs before the amdgpu failure, I also found this, which sounds possibly related, although this is getting beyond my level of PCI jargon proficiency so I can't analyse it in depth. 512 ��� [ 1.053284] pci 0000:01:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window 513 ��� [ 1.053289] pci 0000:00:15.0: BAR 0: assigned [mem 0x4010000000-0x4010000fff 64bit] 514 ��� [ 1.053365] pci 0000:00:15.1: BAR 0: assigned [mem 0x4010001000-0x4010001fff 64bit] 515 ��� [ 1.053379] pci 0000:00:1f.5: BAR 0: assigned [mem 0x6ea20000-0x6ea20fff] 516 ��� [ 1.053389] pci 0000:01:00.0: BAR 6: assigned [mem 0x6e960000-0x6e97ffff pref] Here it seems that the BAR 6 from the AMD GPU tries to get to one memory-mapped location, and ends up in another due to a "bridge window" issue. Not sure if the amdgpu driver is meant to tolerate this well. --- Also, even earlier in the log, there are some ACPI errors that come from the PCI Root Bridge [PC00], which may or may not be related to the power management errors that I see later on: 347 ��� [ 0.913731] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGON.PBGE], AE_NOT_FOUND (20210604/psargs-330) 348 ��� [ 0.913743] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_NOT_FOUND) (20210604/psparse-529) 349 ��� [ 0.913749] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_NOT_FOUND) (20210604/psparse-529) [...] 434 ��� [ 1.001774] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGOF.PBGE], AE_NOT_FOUND (20210604/psargs-330) 435 ��� [ 1.001784] ACPI Error: Aborting method \_SB.PC00.PGOF due to previous error (AE_NOT_FOUND) (20210604/psparse-529) 436 ��� [ 1.001790] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._OFF due to previous error (AE_NOT_FOUND) (20210604/psparse-529) Hope this helps. -- You are receiving this mail because: You are on the CC list for the bug.