Description of problem: I left my computer, it probably entered the stand-by state. While I was waking up the computer it was unresponsive and showed a black screen. I had to reset. Version-Release number of selected component: xorg-x11-server-Xwayland-23.2.6-1.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=ad48d6c58da640b4a98644060598d031;i=66a18;b=98215f55e0b444fa81af3f2284d10117;m=6f6af15ae;t=61767c6e18511;x=23994b8c74fa2136 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.5M3LN2 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.8.7-300.fc40.x86_64 package: xorg-x11-server-Xwayland-23.2.6-1.fc40 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-23.2.6-1.fc40.x86_64 (Fedora Project) 1714060077 backtrace_rating: 3 crash_function: amdgpu_cs_submit_ib comment: I left my computer, it probably entered the stand-by state. While I was waking up the computer it was unresponsive and showed a black screen. I had to reset. Truncated backtrace: Thread no. 1 (9 frames) #14 amdgpu_cs_submit_ib at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.c:1633 #15 ac_roll_context at ../src/amd/common/ac_gather_context_rolls.c:51 #16 ac_ib_gather_context_rolls at ../src/amd/common/ac_gather_context_rolls.c:153 #17 ac_gather_context_rolls at ../src/amd/common/ac_gather_context_rolls.c:307 #18 mesa_cache_db_multipart_set_size_limit at ../src/util/mesa_cache_db_multipart.c:79 #19 _mesa_is_legal_color_format at ../src/mesa/main/fbobject.c:779 #20 ?? #21 ?? #22 ??
Created attachment 2030696 [details] File: proc_pid_status
Created attachment 2030697 [details] File: maps
Created attachment 2030698 [details] File: limits
Created attachment 2030699 [details] File: environ
Created attachment 2030700 [details] File: open_fds
Created attachment 2030701 [details] File: mountinfo
Created attachment 2030702 [details] File: os_info
Created attachment 2030703 [details] File: cpuinfo
Created attachment 2030704 [details] File: core_backtrace
Created attachment 2030705 [details] File: var_log_messages
Created attachment 2030706 [details] File: backtrace
From the backtrace and the description in comment 0, that seems to be a driver issue, moving to Mesa.