Sometimes after my machine resumes from suspend my display stays off with no signal, and USB keyboard (Num lock) and mouse doesn't react. This time I managed to SSH into the machine and gather some logs after it failed resuming. I have experienced this with different kernels and under different Linux operating systems, like Debian and Gentoo, but it is not happening often enough for me to sense a pattern. I will attach log files to the best of my abilities according to: https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html
Created attachment 145563 [details] dmesg output after wakeup
Created attachment 145564 [details] basic info
Created attachment 145565 [details] demidecode output
Created attachment 145566 [details] lsinitramfs output
Created attachment 145567 [details] lshw log
Created attachment 145568 [details] lsmod amdgpu
Created attachment 145569 [details] lspic -nn output
Created attachment 145570 [details] lspci -vnn output
Created attachment 145571 [details] modinfo amdgpu output
Created attachment 145572 [details] package log output
Created attachment 145573 [details] uname -a output
Created attachment 145574 [details] Xorg log
Can confirm this problem on kernel-5.2.17-200.fc30 kernel-5.2.9-200.fc30 kernel-5.2.5-200.fc30 kernel-5.3.1-150.vanilla.knurd.1.fc30 Suspend & resume work flawlessly on kernel-4.20.16-200.fc29
Can you bisect?
Is there a Fedora workflow for bisecting? Also, do I need to take care of any GPU firmware or is it just the kernel?
(In reply to me from comment #15) > Is there a Fedora workflow for bisecting? > Also, do I need to take care of any GPU firmware or is it just the kernel? Don't worry about the firmware, just the kernel is fine. Here's a bisect howto tailored to fedora: https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
The kernel-package.py script is broken. I'll build kernels directly. Git bisect says approximately 13 steps are required between v4.20 and v5.0. Will report back in ~14 days when that's done (bug manifests only after some uptime).
Bisection turns out to be harder than anticipated because there is another bug that makes the system freeze on suspend (not reported yet). Anyways, this seems to be a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=111729#c7
Potential fix (and kernel Bugzilla bug): https://bugzilla.kernel.org/show_bug.cgi?id=204241
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/923.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.