Screen goes black looks like struck down

Ask Fedora
, , , ,
1

while I was opening computer , screen goes black after login prompt i need to restart forcefully.
OS : fedora silverblue x86_64
hardware information:-
kernel:- 6.3.11-200.fc38.x86_64
gnome version :- 44.2
Display compositor:- wayland
processor:- AMD Ryzen™ 5 5500U with Radeon™ Graphics × 12
graphics:- AMD Radeon™ Graphics
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne (rev c2)

journalctl -b -1 (only two red alerting line)

Jul 11 02:28:14 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SBRG.EC0], AE_NOT_FOUND (20221020/dswload2-162)

Jul 11 02:28:14 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)

Jul 11 02:28:14 fedora kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
1 Like
2

after unlocking the screen becomes black , looks like the system has crashed . it repeatedly happened. i was trying some trial and errors to find out where is the exact problem is lying . i found may be the issue is with wayland display compositor because when i opened it with x11, I found the issue is resolved…

journalctl -b -1 |grep wayland (some lines i thought may be important) :-

Jul 10 23:23:19 fedora gnome-shell[1180]: Connection to xwayland lost

Jul 10 23:23:19 fedora org.gnome.Shell.desktop[1180]: GNOME Shell terminated with an error: Xwayland exited unexpectedly

Jul 10 23:23:19 fedora /usr/libexec/gdm-wayland-session[1153]: dbus-daemon[1153]: [session uid=42 pid=1153] Activating service name='org.freedesktop.systemd1' requested by ':1.11' (uid=42 pid=1296 comm="/usr/libexec/gsd-sharing" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")

Jul 10 23:23:19 fedora gnome-shell[1180]: Xwayland terminated, exiting since it was mandatory
3

Same CPU, after last update screen freezes. Sometimes on boot, sometimes on desktop, rolled back to previous deploy, works fine.

4

TLDR for affected AMD Ryzen users:

Roll back to linux kernel 6.3.8 until fixes have been applied yet-to-be-released 6.4.4 or later.

Also consider adjusting /etc/dnf/dnf.conf to increase number of kernels to retain and/or version-lock your kernel.

Details:

5

Just leaving a note here that the issue has been resolved in kernel 6.4.4-200.fc38