Suspending the laptop is not the issue I am experiencing but waking the laptop after suspension is what breaks. The laptop wakes up to a black screen without a functioning system, not even CTRL+ALT+BACKSPACE works. The issue is similar to https://bbs.archlinux.org/viewtopic.php?id=249510 and therefore I have tried all the solutions mentioned in that thread (before knowing of its existence). I also tried the Early KMS solution suggested by the owner of that thread, which I did not think of and the result remained the same. Solutions mentioned in https://wiki.archlinux.org/index.php/Laptop/Lenovo#E_series has also been tried but the problem remains unsolved.
Something worth mentioning is that the laptop has to go through suspension and waking up twice for the system to return to normal, but this solution works 20% of the times and has unfortunately caused me loss of important data.
1. https://git.io/Jer5J (lshw -short)
2. https://git.io/Jer7H (Journalctl --since="1 hour ago", note that this journalctl includes several boots because I was trying to include the functional two suspends for the system to work again)
3. https://git.io/Jer7S (dmesg)
4. https://git.io/Jer79 (Xorg.0.log)
From the above log files, V1del (https://bbs.archlinux.org/viewtopic.php?pid=1873276#p1873276), was able to identify crashes in my AMDGPU driver thus leading me to create this bug hoping for a fix!
Does it work with kernel 5.4? There were several fixes for resume that were added (which will be making their way back to stable kernels).
(In reply to Alex Deucher from comment #1)
> Does it work with kernel 5.4? There were several fixes for resume that were
> added (which will be making their way back to stable kernels).
Can't answer this question until kernel 5.4 has been pushed to the Arch Linux repositories. Will report back when I receive an update!
-- 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/959.