Bug 1332484 - [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGSEGV
Summary: [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 23
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:1b5312926ffbbb652229e1e86b8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 10:14 UTC by Paulo Fidalgo
Modified: 2016-12-20 20:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:15:17 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (76.44 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: cgroup (200 bytes, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: core_backtrace (8.16 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: dso_list (40.50 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: environ (1.70 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: limits (1.29 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: maps (209.91 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: mountinfo (3.64 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: namespaces (85 bytes, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: open_fds (187 bytes, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: proc_pid_status (1.05 KB, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details
File: var_log_messages (296 bytes, text/plain)
2016-05-03 10:14 UTC, Paulo Fidalgo
no flags Details

Description Paulo Fidalgo 2016-05-03 10:14:34 UTC
Description of problem:
I was just doing regular working when it crashed...

Version-Release number of selected component:
plasma-workspace-5.5.5-5.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/plasmashell --shut-up
crash_function: KCrash::defaultCrashHandler
executable:     /usr/bin/plasmashell
global_pid:     2255
kernel:         4.4.8-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler at /usr/src/debug/kcrash-5.21.0/src/kcrash.cpp:431
 #3 get_stencil_miptree at brw_misc_state.c:227
 #4 brw_workaround_depthstencil_alignment at brw_misc_state.c:243
 #5 brw_clear at brw_clear.c:234
 #6 QSGBatchRenderer::Renderer::renderBatches at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2475
 #7 QSGBatchRenderer::Renderer::render at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2699
 #8 QSGRenderer::renderScene at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/scenegraph/coreapi/qsgrenderer.cpp:217
 #10 QSGRenderContext::renderNextFrame at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/scenegraph/qsgcontext.cpp:555
 #11 QQuickWindowPrivate::renderSceneGraph at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/items/qquickwindow.cpp:424
 #12 QSGGuiThreadRenderLoop::renderWindow at /usr/src/debug/qtdeclarative-opensource-src-5.6.0/src/quick/scenegraph/qsgrenderloop.cpp:396

Potential duplicate: bug 1285871

Comment 1 Paulo Fidalgo 2016-05-03 10:14:41 UTC
Created attachment 1153317 [details]
File: backtrace

Comment 2 Paulo Fidalgo 2016-05-03 10:14:42 UTC
Created attachment 1153318 [details]
File: cgroup

Comment 3 Paulo Fidalgo 2016-05-03 10:14:44 UTC
Created attachment 1153319 [details]
File: core_backtrace

Comment 4 Paulo Fidalgo 2016-05-03 10:14:46 UTC
Created attachment 1153320 [details]
File: dso_list

Comment 5 Paulo Fidalgo 2016-05-03 10:14:47 UTC
Created attachment 1153321 [details]
File: environ

Comment 6 Paulo Fidalgo 2016-05-03 10:14:49 UTC
Created attachment 1153322 [details]
File: limits

Comment 7 Paulo Fidalgo 2016-05-03 10:14:51 UTC
Created attachment 1153323 [details]
File: maps

Comment 8 Paulo Fidalgo 2016-05-03 10:14:53 UTC
Created attachment 1153324 [details]
File: mountinfo

Comment 9 Paulo Fidalgo 2016-05-03 10:14:54 UTC
Created attachment 1153325 [details]
File: namespaces

Comment 10 Paulo Fidalgo 2016-05-03 10:14:56 UTC
Created attachment 1153326 [details]
File: open_fds

Comment 11 Paulo Fidalgo 2016-05-03 10:14:57 UTC
Created attachment 1153327 [details]
File: proc_pid_status

Comment 12 Paulo Fidalgo 2016-05-03 10:14:58 UTC
Created attachment 1153328 [details]
File: var_log_messages

Comment 13 Rex Dieter 2016-05-03 12:06:22 UTC
brw_clear  intel driver crash, triaging there

Comment 14 Paulo Fidalgo 2016-05-03 13:01:21 UTC
(In reply to Rex Dieter from comment #13)
> brw_clear  intel driver crash, triaging there

Yes I have a lot of crashes in intel driver, but since my kernel is tainted I cannot report them. Also I cannot found the origin of the taint.

[    2.404338] CPU: 0 PID: 101 Comm: kworker/u8:2 Not tainted 4.4.8-300.fc23.x86_64 #1
[    4.665263] CPU: 0 PID: 661 Comm: systemd-udevd Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[  122.839109] CPU: 3 PID: 1161 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[  122.857368] CPU: 3 PID: 1161 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[ 1200.888174] CPU: 0 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[12845.615064] CPU: 3 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[14023.540910] CPU: 3 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[29765.339070] CPU: 0 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[30681.134632] CPU: 2 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[41491.049066] CPU: 3 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[42810.761036] CPU: 3 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[45103.263569] CPU: 3 PID: 8564 Comm: kworker/u8:88 Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[45678.141794] CPU: 3 PID: 9397 Comm: kworker/u8:59 Tainted: G        W       4.4.8-300.fc23.x86_64 #1
[60548.890548] CPU: 0 PID: 1975 Comm: Xorg Tainted: G        W       4.4.8-300.fc23.x86_64 #1

cat /proc/sys/kernel/tainted
512

cat /proc/modules | awk {'print $1'} | xargs modinfo | grep license  | grep -v GPL | wc -l
0

So all my modules are GPL and event that I have a tainted kernel. I can help debug if needed.

Comment 15 Fedora End Of Life 2016-11-25 08:55:17 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 16 Fedora End Of Life 2016-12-20 20:15:17 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.


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