Bug 1251797

Summary: [abrt] gnome-shell: get_radeon_bo(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Dan Loomis <danloomis47>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/831a5058fbae6bf76fcf0cfe1dff8e25c61ee8a6
Whiteboard: abrt_hash:29f8d90901791f734616a42f3a968ae38e39e84c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:26:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Dan Loomis 2015-08-10 01:07:40 UTC 
Description of problem:
This happened while I was away from the system.    Might be related to the screen going dark after thirty mins.

Version-Release number of selected component:
gnome-shell-3.16.3-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: get_radeon_bo
executable:     /usr/bin/gnome-shell
global_pid:     2083
kernel:         4.1.3-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 get_radeon_bo at radeon_drm_bo.c:90
 #1 radeon_drm_get_cs_handle at radeon_drm_bo.c:823
 #2 radeon_cs_create_fence at radeon_drm_cs.c:615
 #3 radeon_drm_cs_flush at radeon_drm_cs.c:476
 #4 si_context_gfx_flush at si_hw_context.c:104
 #5 st_finish at state_tracker/st_cb_flush.c:98
 #6 st_AllocTextureImageBuffer at state_tracker/st_cb_texture.c:521
 #7 st_TexImage at state_tracker/st_cb_texture.c:875
 #8 teximage at main/teximage.c:3364
 #9 _mesa_TexImage2D at main/teximage.c:3403
Comment 1 Dan Loomis 2015-08-10 01:07:44 UTC 
Created attachment 1060854 [details]
File: backtrace
Comment 2 Dan Loomis 2015-08-10 01:07:45 UTC 
Created attachment 1060855 [details]
File: cgroup
Comment 3 Dan Loomis 2015-08-10 01:07:46 UTC 
Created attachment 1060856 [details]
File: core_backtrace
Comment 4 Dan Loomis 2015-08-10 01:07:47 UTC 
Created attachment 1060857 [details]
File: dso_list
Comment 5 Dan Loomis 2015-08-10 01:07:48 UTC 
Created attachment 1060858 [details]
File: environ
Comment 6 Dan Loomis 2015-08-10 01:07:49 UTC 
Created attachment 1060859 [details]
File: limits
Comment 7 Dan Loomis 2015-08-10 01:07:53 UTC 
Created attachment 1060860 [details]
File: maps
Comment 8 Dan Loomis 2015-08-10 01:07:54 UTC 
Created attachment 1060861 [details]
File: mountinfo
Comment 9 Dan Loomis 2015-08-10 01:07:55 UTC 
Created attachment 1060862 [details]
File: namespaces
Comment 10 Dan Loomis 2015-08-10 01:07:56 UTC 
Created attachment 1060863 [details]
File: open_fds
Comment 11 Dan Loomis 2015-08-10 01:07:57 UTC 
Created attachment 1060864 [details]
File: proc_pid_status
Comment 12 Dan Loomis 2015-08-10 01:07:58 UTC 
Created attachment 1060865 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 17:26:39 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.