https://bugzilla.kernel.org/show_bug.cgi?id=204975 Alex Williamson (alex.williamson@xxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.williamson@xxxxxxxxxx --- Comment #7 from Alex Williamson (alex.williamson@xxxxxxxxxx) --- When we get the "stuck in D3" message, it usually means that we're getting back -1 on config space reads rather than the device is actually stuck in D3. The -1 return probably means the downstream bus never recovered when we issued a secondary bus reset to perform a reset on the GPU. This seems to be common with AGESA updates and AFAICT indicates a hardware/firmware issue, not a kernel issue. As you indicate, it worked previously and started failing after BIOS update. This is the common story, AMD needs to fix secondary bus reset support on their root ports. I believe some users have had success rolling back their BIOS to a previous release. -- You are receiving this mail because: You are watching the assignee of the bug.
