Bug 1053407

Summary: SIGSEGV intel_miptree_attach_map at intel_mipmap_tree.c:836
Product: [Fedora] Fedora Reporter: Peter Lemenkov <lemenkov>
Component: mesaAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: 306power, ajax, filipesbim, fixps7061, gordon, ignatenko, ivanuz21, mkasik, pacree, prd-fedora, ref-hoffmann, sagarun, temlakos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:28:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Lemenkov 2014-01-15 08:08:34 UTC
A common issue in Mesa's intel driver sigkills random applications. See FDo's ticket for further details.

I can easily reproduce it with Cheese application.


Truncated backtrace:
Thread no. 1 (10 frames)
 #0 intel_miptree_attach_map at intel_mipmap_tree.c:836
 #1 intel_miptree_map at intel_mipmap_tree.c:877
 #2 intel_map_renderbuffer at intel_fbo.c:129
 #3 map_attachment at ../../../src/mesa/swrast/s_renderbuffer.c:578
 #4 _swrast_map_renderbuffers at ../../../src/mesa/swrast/s_renderbuffer.c:652
 #5 _swrast_render_start at ../../../src/mesa/swrast/s_context.c:895
 #6 _swsetup_RenderStart at ../../../src/mesa/swrast_setup/ss_context.c:202
 #7 run_render at ../../../src/mesa/tnl/t_vb_render.c:276
 #8 _tnl_run_pipeline at ../../../src/mesa/tnl/t_pipeline.c:163
 #9 intelRunPipeline at intel_tris.c:1097

Comment 1 Peter Lemenkov 2014-01-15 08:09:53 UTC
*** Bug 1003182 has been marked as a duplicate of this bug. ***

Comment 2 Peter Lemenkov 2014-01-15 08:10:46 UTC
Btw this issue exists since F19 at least.

Comment 3 Peter Lemenkov 2014-01-15 08:11:24 UTC
*** Bug 1007973 has been marked as a duplicate of this bug. ***

Comment 4 Peter Lemenkov 2014-01-15 08:11:44 UTC
*** Bug 1029626 has been marked as a duplicate of this bug. ***

Comment 5 Peter Lemenkov 2014-01-15 08:13:03 UTC
*** Bug 1007963 has been marked as a duplicate of this bug. ***

Comment 6 Peter Lemenkov 2014-01-15 08:13:38 UTC
*** Bug 1023498 has been marked as a duplicate of this bug. ***

Comment 7 Peter Lemenkov 2014-01-15 08:15:45 UTC
*** Bug 1000178 has been marked as a duplicate of this bug. ***

Comment 8 Igor Gnatenko 2014-01-15 08:21:36 UTC
*** Bug 1012128 has been marked as a duplicate of this bug. ***

Comment 9 Igor Gnatenko 2014-01-15 08:21:37 UTC
*** Bug 1018878 has been marked as a duplicate of this bug. ***

Comment 10 Felix Schwarz 2015-03-28 21:05:06 UTC
*** Bug 1055255 has been marked as a duplicate of this bug. ***

Comment 11 Felix Schwarz 2015-03-28 21:06:25 UTC
*** Bug 1206790 has been marked as a duplicate of this bug. ***

Comment 12 Fedora End Of Life 2015-05-29 10:30:35 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2015-06-29 14:28:05 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.