FS#77418 - Blank screen or flashing screen when resuming from sleep or hibernate or when TV has been off for a

Attached to Project: Arch Linux
Opened by Kris (sarvasana) - Tuesday, 07 February 2023, 09:43 GMT
Last edited by Toolybird (Toolybird) - Friday, 05 May 2023, 21:24 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


Blank screen when resuming from sleep or hibernate or when TV has been off for a while

Originally raised with KDE: https://bugs.kde.org/show_bug.cgi?id=465403.
KDE developers think it is a kernel defect and asked to raise it upstream.
Kernel.org suggests to raise kernel defects at the correct distribution.

1. Boot
2. Login
3. Sleep or Hibernate
4. Wait for TV to go a sleep or switch off (Samsung Neo QLED QN90B 43")
5. Resume
6. You reached the failure state

The screen is white or flickering between white and rendering the lock screen.
Login works. Typing in kwin_x11 --replace sometimes works and then the system can be used again.
Most of the times the system does not recover and a reboot is required.

I used KDE Connect to unlock and execute kwin_x11 --replace also.
This sometimes also works as a work arround.

Rendering the lock screen normally and resume the system in a usable state.

Linux/KDE Plasma: 6.1.9-arch1-2 (64-bit)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 05 May 2023, 21:24 GMT
Reason for closing:  Upstream
Additional comments about closing:  If still happening, please follow up in the upstream ticket.
Comment by Kris (sarvasana) - Tuesday, 07 February 2023, 09:47 GMT
See KDE comment:

Comment contents:
"The fact that restarting kwin_x11 doesn't help all the time and it also happens on wayland sounds like it's most likely a bug in the kernel.
If you use nvidia, try reporting the issue to nvidia developers; otherwise please report this issue upstream to kernel developers."
Comment by Kris (sarvasana) - Tuesday, 07 February 2023, 15:25 GMT
From journalctl:

feb 07 14:34:49 anon xdg-desktop-portal-kde[123678]: qt.qpa.xcb: could not connect to display
feb 07 14:34:49 anon audit[123678]: ANOM_ABEND auid=0 uid=0 gid=0 ses=5 pid=123678 comm="xdg-desktop-por" exe="/usr/lib/xdg-desktop-portal-kde" sig=6 res=1
feb 07 14:34:49 anon xdg-desktop-portal-kde[123678]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
feb 07 14:34:49 anon xdg-desktop-portal-kde[123678]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Comment by Toolybird (Toolybird) - Tuesday, 07 February 2023, 20:21 GMT
Is this a regression i.e. it used to work? If yes, you'll need to debug it [1]. Please try different kernels (earlier, lts, mainline, etc) to see if the problem can be reproduced. General kernel troubleshooting advice [2]. Please let us know what you find out.

[1] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
[2] https://wiki.archlinux.org/title/Kernel#Troubleshooting
Comment by Kris (sarvasana) - Wednesday, 08 February 2023, 04:47 GMT
This is a new install on a new device and it always failed.

I did try 5.15.91-4-lts and there the problem is not present.
So between 5.15.91-4-lts and 6.1.9-arch1-2 something went pear-shaped.

About this machine:
UM690 Version 1.0.
CPU: AMD Ryzen 9 6900HX with Radeon Graphics (16) @ 3.300GHz
GPU: AMD ATI Radeon 680M

I also have a laptop, also AMD, which I can hookup to the same screen and test the both kernels.
Would that make sense?
Comment by Kris (sarvasana) - Wednesday, 08 February 2023, 08:55 GMT
I also tested my laptop, there the issue does not occur.

Host: 82A2 Yoga Slim 7 14ARE05
Kernel: 6.1.9-arch1-2
CPU: AMD Ryzen 7 4800U with Radeon Graphics (16) @ 1.800GHz
GPU: AMD ATI 03:00.0 Renoir
Comment by Kris (sarvasana) - Monday, 06 March 2023, 05:00 GMT
Now also present on 6.1.15-1-lts.
Comment by Toolybird (Toolybird) - Monday, 06 March 2023, 06:34 GMT
You've confirmed it's a kernel regression. Aforementioned links are still relevant. amdgpu / radeon kernel bugs can be reported here [1]

[1] https://gitlab.freedesktop.org/drm/amd
Comment by Kris (sarvasana) - Monday, 06 March 2023, 10:22 GMT Comment by Toolybird (Toolybird) - Wednesday, 05 April 2023, 22:00 GMT
Still happening with latest kernels? Progress seems stalled in the upstream issue.
Comment by Kris (sarvasana) - Thursday, 06 April 2023, 10:43 GMT
Yes, the problem is still there on latest kernels.
Upstream has asked me to test if amdgpu 6.3-rc1 or later fixes the problem.

I did not have a chance to test this yet and am actually unsure how to do this.
Probably would take the PKGBUILD of amdgpu-git and change it to some other commit and then install.

Would have to this on my own production machine, which I use for work daily.
Will see what I can do.