Thanks @pheiduck.
Do you know if this issue is being worked on?
I don’t mind waiting a while for a fix, but just to know that it’s in a bug list somewhere would give peace of mind.
@Riquez
I unfortunately didn’t see anything in the patch waiting list that suggests a fix for the problem.:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.19/series
Bad news on 6.0-rc2 issue is present there as well.
but qemu does not represents real regressions because it still happened on 5.15.62
but I don’t have it on Host System.
And I think its Bluetooth related, because there is a workaround from the Arch Linux Guys.:
https://wiki.archlinux.org/title/Bluetooth#Bluetooth_immediately_waking_up_suspend-to-idle_devices
but this breaks normal power off / reboot on my side.
https://groups.google.com/g/linux.debian.bugs.dist/c/bSV8CfLg-HQ?pli=1
Maybe this
https://lkml.org/lkml/2022/8/16/1413
Cause this regression but not sure.
The story has an end: 5.19.4 is out and has many suspend/resume fixes. 
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.4
Very soon it will be on stable so you can test it before.
1 Like
Hi sorry for the slow reply. Unfortunately 5.19.4 still has black screen on wake in my Archcraft partition.
I don’t want to switch Manjaro from Stable as I use it daily, but I think its fair to say the result will be the same. Both systems were affected in an identical way with 5.19
Sound very weird, I hope they have a patch later on, for 6.0 and up. Until then I recommend to use latest LTS Kernel.
Next round w/ some suspend / resume fixups.
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.6
commit 8e3ba23a67de984f4156f0663f1f603ff6c15815
Author: Karol Herbst kherbst@redhat.com
Date: Fri Aug 19 22:09:28 2022 +0200
nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf
commit 6b04ce966a738ecdd9294c9593e48513c0dc90aa upstream.
It is a bit unlcear to us why that’s helping, but it does and unbreaks
suspend/resume on a lot of GPUs without any known drawbacks.
5.19.6 on Archcraft & I still cannot wake from suspend 
Im starting to worry about this now, I might have to buy a new computer 
this one is only 13 months old!
I don’t think so, just use LTS Kernel the next one will not have this bug.
The trouble is 5.15 doesnt have my wifi driver, so it’s not a great option either way. Although buying a wifi dongle is probably a way out.
Which one do you have?
lspci | grep -i wireless
Maybe there is an external driver available
yes there is, its the realtek 8852ae (rtw89 driver on github)
I used that before it became incorporated into 5.16+.
I re-installed Manjaro a few months ago after some update issues & didn’t need the git driver any longer.
There are some upkeep hassles of those drivers such as needing to re-install after kernel updates & use ethernet or USB tethering to get back online. Which I suppose isn’t too bad, but I breathed a sigh of relief when I didn’t need to worry those rituals any longer.
Update 2022.09.15: 5.19.8-arch1-1 still black screen suspend ~ whatever happened to the no regression mantra 
2022.09.28: Kernel 5.19.11 also continues with this bug. Just keeping a record ~
2 Likes
Have you tried putting “shallow” sleep in grub? Not as power-saving as a “deep” sleep, but it shuts down wifi, usb, and black-blanks the display.
I have to use it with Manjaro/GPD Pocket 3. Gives me enough savings to get through the day, and it’d be interesting to see if your problem can be replicated with the different forms of suspend.
This problem may be fixed now… it was also discussed at the Kernel Summit (LPC)
Interesting. I’ve been having “black screen” problems (though not suspend-related; screen would just sudden go black for no reason) with 5.19 myself ever since I updated 5.18 → 5.19 a few days ago. I just downgraded 5.19 → 5.18 and we’ll see if the problem stops. (If it does, it’s a kernel bug. If not, it’s my MB or CPU flaking out.)
And I think its Bluetooth related, because there is a …
This solved the problem for me.
I never encountered that “black screen on wake-up” problem since I bought my ZenBook with Ryzen 7 5800U, more than a year ago. But a few days ago the problem appeared. I tried all the kernels I used before the problem appeared, but to no avail. Then, after reading your hint, I deactivated Bluetooth, et voilà: Wake-up is working flawlessly again.
Thank you very much.
I use 5.19.13 and it worked again on my machine 
Unforutunately still broken for me with 5.19.13 & 5.19.14
FIXED!
In my case it seems I am victim of 2 converging issues, the 5.19 kernel & the original kernel param, mentioned right at the top of this thread: iommu=soft.
The marvellous & diligent Luc Raymond has once again come to the rescue for people with problematic Lenovo AMD. Those using kernel param iommu=soft should exchange it for amd_iommu=off
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.