[Bug 204241] amdgpu fails to resume from suspend
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Feb 25 03:06:24 UTC 2020
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #53 from Alexander Jones (acjones8 at hawaii.edu) ---
(In reply to dimitris from comment #52)
> This is a shot in the dark/cargo culting it, but in case it helps:
>
> I had a very similar problem on a T495 (Ryzen 3700U), running Fedora 31,
> which resolved itself when the 5.4 series was available in Fedora.
>
> Before 5.4 was available, I came across reports linking this to a USB
> controller of all things, like
> https://www.mail-archive.com/debian-kernel@lists.debian.org/msg116563.html.
>
> In my case the cuprit was:
>
> 06:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
>
> so I started removing the device from the PCI tree before suspend using
> /sys/bus/pci/devices/0000:06:00.4/remove and rescanning the PCI bus on
> resume. First manually and later though a systemd hook. That worked around
> the problem until 5.4 "fixed" this.
Thank you for the suggestion! I tried that out on my ThinkPad, disabling all of
my USB devices just in case. They are:
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI
Controller (rev 20)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
Controller (rev 49)
01:00.4 USB controller: Realtek Semiconductor Co., Ltd. Device 816d (rev 0e)
Unfortunately, this didn't fix the suspend issue, I still get the glitchy
screen. On a whim, I tried to disable Bluetooth in the BIOS, as well as the
Fingerprint Scanner and TPM chip, but that also didn't have any affect.
Coincidentally, I DID hear Kmail pop a notification after resuming, so it seems
it's not as dead as I thought, the kernel and even the userland seem to still
work then. Must be AMDGPU or something else in the graphics stack that dies,
since I can't switch to a VT and suspending while in a VT doesn't work either,
and results in the same glitched out mess.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list