Bug 2278223 - [abrt] xorg-x11-server-Xwayland: amdgpu_cs_submit_ib(): Xwayland killed by SIGABRT
Summary: [abrt] xorg-x11-server-Xwayland: amdgpu_cs_submit_ib(): Xwayland killed by SI...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:d2121349838707080d4c79abf88...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-01 17:33 UTC by sjoerdschouten
Modified: 2024-05-02 14:13 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.49 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: maps (3.99 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: limits (1.29 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: environ (1.45 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: open_fds (13.39 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: mountinfo (3.25 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: os_info (734 bytes, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: cpuinfo (3.33 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: core_backtrace (35.28 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: var_log_messages (1.82 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details
File: backtrace (93.15 KB, text/plain)
2024-05-01 17:33 UTC, sjoerdschouten
no flags Details

Description sjoerdschouten 2024-05-01 17:33:43 UTC
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 ??

Comment 1 sjoerdschouten 2024-05-01 17:33:45 UTC
Created attachment 2030696 [details]
File: proc_pid_status

Comment 2 sjoerdschouten 2024-05-01 17:33:47 UTC
Created attachment 2030697 [details]
File: maps

Comment 3 sjoerdschouten 2024-05-01 17:33:48 UTC
Created attachment 2030698 [details]
File: limits

Comment 4 sjoerdschouten 2024-05-01 17:33:49 UTC
Created attachment 2030699 [details]
File: environ

Comment 5 sjoerdschouten 2024-05-01 17:33:51 UTC
Created attachment 2030700 [details]
File: open_fds

Comment 6 sjoerdschouten 2024-05-01 17:33:52 UTC
Created attachment 2030701 [details]
File: mountinfo

Comment 7 sjoerdschouten 2024-05-01 17:33:53 UTC
Created attachment 2030702 [details]
File: os_info

Comment 8 sjoerdschouten 2024-05-01 17:33:54 UTC
Created attachment 2030703 [details]
File: cpuinfo

Comment 9 sjoerdschouten 2024-05-01 17:33:56 UTC
Created attachment 2030704 [details]
File: core_backtrace

Comment 10 sjoerdschouten 2024-05-01 17:33:57 UTC
Created attachment 2030705 [details]
File: var_log_messages

Comment 11 sjoerdschouten 2024-05-01 17:33:58 UTC
Created attachment 2030706 [details]
File: backtrace

Comment 12 Olivier Fourdan 2024-05-02 14:13:38 UTC
From the backtrace and the description in comment 0, that seems to be a driver issue, moving to Mesa.


Note You need to log in before you can comment on or make changes to this bug.