| Summary: | kwin-4.7.0 with OpenGL ES crashes sometimes with new xf86-video-intel-2.16.0 drivers | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Sven Eden <sven> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | crash | CC: | sven |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Sven Eden
2011-08-18 10:17:49 UTC
Created attachment 62930 [details]
New crash information added by DrKonqi
kwin (4.7.00 (4.7.0)) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.3
- What I was doing when the application crashed:
Opened Kalendar via ctrl-F2. kwin crashed, restarted, and the Kalendar was displayed.
- Custom settings of the application:
Desktop Effects were enabled
- State of kwin:
kwin-4.7.0 has been compiled with GLES instead of OpenGL support. For this to work mesa had to be compiled without gallium support (or the intel video portion crashes kwin on load, gallium-intel is far from ready) and worked flawlessly with the previous version of the intel drivers
- Installed versions:
kwin - 4.7.0
libdrm - 2.4.26
mesa - 7.11
xf86-video-intel - 2.16.0
xorg-server - 1.10.3
-- Backtrace (Reduced):
#8 0x00007f567533b1c3 in dri2_destroy_image_khr () from /usr/lib64/libEGL.so.1
#9 0x00007f5675332ec5 in eglDestroyImageKHR () from /usr/lib64/libEGL.so.1
#10 0x00007f5678063e36 in KWin::SceneOpenGL::Texture::load(unsigned long const&, QSize const&, int, QRegion) () from /usr/lib64/libkdeinit4_kwin.so
#11 0x00007f567806404b in KWin::SceneOpenGL::Window::bindTexture() () from /usr/lib64/libkdeinit4_kwin.so
#12 0x00007f56780682c0 in KWin::SceneOpenGL::Window::performPaint(int, QRegion, KWin::WindowPaintData) () from /usr/lib64/libkdeinit4_kwin.so
Created attachment 62931 [details]
New crash information added by DrKonqi
kwin (4.7.00 (4.7.0)) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.3
- What I was doing when the application crashed:
Hovered on an Icon in the folder view of my Desktop folder
- Custom settings of the application:
Desktop Effects were enabled
- State of kwin:
kwin-4.7.0 has been compiled with GLES instead of OpenGL support. For this to work mesa had to be compiled without gallium support (or the intel video portion crashes kwin on load, gallium-intel is far from ready) and worked flawlessly with the previous version of the intel drivers
- Installed versions:
kwin - 4.7.0
libdrm - 2.4.26
mesa - 7.11
xf86-video-intel - 2.16.0
xorg-server - 1.10.3
- Further notes:
All those three crashes happened exactly once. When I tried to reproduce them, kwin remained running. But I have disabled the desktop effects for now.
-- Backtrace (Reduced):
#8 0x00007ffee28db1c3 in dri2_destroy_image_khr () from /usr/lib64/libEGL.so.1
#9 0x00007ffee28d2ec5 in eglDestroyImageKHR () from /usr/lib64/libEGL.so.1
#10 0x00007ffee5603e36 in KWin::SceneOpenGL::Texture::load(unsigned long const&, QSize const&, int, QRegion) () from /usr/lib64/libkdeinit4_kwin.so
#11 0x00007ffee560404b in KWin::SceneOpenGL::Window::bindTexture() () from /usr/lib64/libkdeinit4_kwin.so
#12 0x00007ffee56082c0 in KWin::SceneOpenGL::Window::performPaint(int, QRegion, KWin::WindowPaintData) () from /usr/lib64/libkdeinit4_kwin.so
Sorry for _another_ post. I forgot to mention, that since the second crash krunner does not work any more. The process is there, but it does not react to neither desktop context menu entry to start a program, nor ctrl-F2 key combination. Weird. Created attachment 63704 [details]
New crash information added by DrKonqi
kwin (4.7.1 (4.7.1)) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.3
- What I was doing when the application crashed:
Pressed Alt+F2 to open krunner.
- Custom settings of the application:
Intel Drivers 2.16.0 with Intel HD chipset and GLES instead of OpenGL support.
Intel Drivers 2.15.0 work flawlessly with GLES
-- Backtrace (Reduced):
#8 0x0000003fd680d1c3 in dri2_destroy_image_khr () from /usr/lib64/libEGL.so.1
#9 0x0000003fd6804ec5 in eglDestroyImageKHR () from /usr/lib64/libEGL.so.1
#10 0x00007f94c6e99196 in KWin::SceneOpenGL::Texture::load (this=0xcaa6b0, pix=<optimized out>, size=..., depth=<optimized out>, region=<optimized out>) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/scene_opengl_egl.cpp:257
#11 0x00007f94c6e993ab in KWin::SceneOpenGL::Window::bindTexture (this=0xcaa670) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/scene_opengl.cpp:387
#12 0x00007f94c6e9d620 in KWin::SceneOpenGL::Window::performPaint (this=0xcaa670, mask=518, region=..., data=...) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/scene_opengl.cpp:476
> - Custom settings of the application:
> Intel Drivers 2.16.0 with Intel HD chipset and GLES instead of OpenGL support.
> Intel Drivers 2.15.0 work flawlessly with GLES
We cannot do anything about driver crashes. Please report to Intel devs.
Yes, I thought about that, too. The problem: kwin is the only opengl app that crashes. Every OpenGL program I tried worked without any issues. On Saturday 17 September 2011 11:33:42 Sven Eden wrote:
> Yes, I thought about that, too. The problem: kwin is the only opengl app that
> crashes. Every OpenGL program I tried worked without any issues.
Well OpenGL applications use OpenGL, while you chose to use KWin with OpenGL ES 2.0. Which is a major difference.
I have recompiled mesa and kwin to use OpenGL instead of GLES, the result is the same, it crashes. If it is of any interest, I'll add the trace, but that's a bit difficult. When trying with OpenGL kwin crashes so badly, that it does not come back. I'll finish my report on bugs.freedesktop.org referencing this bug, then I'll give the new drivers a try again. Created attachment 63722 [details] New crash information added by DrKonqi kwin (4.7.1 (4.7.1)) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.3 This is one of two Backtraces with OpenGL and the new drivers like mentioned above. There _is_ a bug that is about this issue, in Bug 268186 (found by DrKonqi) someone reported that kwin crashes when direct rendering is disabled. That's the way I have got this trace. When it crashed first I noted that both Direct Rendering and V2 Shaders where disabled. Why, I can't tell, those options have always been enabled and the previous drivers worked properly. Maybe they got automatically disabled due to kwin crashing? Unfortunately when kwin went out for lunch DrKonqi opened twice. I can't tell which one of both traces is more relevant, so I hope you forgive me posting both. Mainly for having Backtraces for the intel devs. (https://bugs.freedesktop.org/show_bug.cgi?id=40962) -- Backtrace (Reduced): #7 0x0000003a37245172 in dri2SwapBuffers (pdraw=0x17f0ec0, target_msc=0, divisor=0, remainder=0) at dri2_glx.c:547 #8 0x0000003a388d8cb5 in KWin::SceneOpenGL::flushBuffer (this=<optimized out>, mask=<optimized out>, damage=...) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/scene_opengl_glx.cpp:530 #9 0x0000003a388d9535 in KWin::SceneOpenGL::paint (this=0x17de500, damage=..., toplevels=<optimized out>) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/scene_opengl_glx.cpp:464 #10 0x0000003a388bc461 in KWin::Workspace::performCompositing (this=0x1ace4e0) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/composite.cpp:432 #11 0x0000003c6af718b9 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 Created attachment 63724 [details]
New crash information added by DrKonqi
kwin (4.7.1 (4.7.1)) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.3
This is the second instance of DrKonqi that opened like mentioned in my previous post
-- Backtrace (Reduced):
#7 0x0000003a37230e38 in __indirect_glProgramParameters4fvNV (target=1, index=46309492, num=47375952, params=<optimized out>) at /usr/include/bits/string3.h:52
#8 0x00007f0b017cd518 in KWin::ARBBlurShader::init (this=0x2c2a060) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/effects/blur/blurshader.cpp:463
#9 0x00007f0b017c9a50 in KWin::BlurEffect::reconfigure (this=0x29909c0, flags=<optimized out>) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/effects/blur/blur.cpp:83
#10 0x00007f0b017c9bcc in KWin::BlurEffect::BlurEffect (this=0x29909c0) at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/effects/blur/blur.cpp:53
#11 0x00007f0b017c9cb6 in KWin::effect_create_kwin4_effect_blur () at /var/tmp/portage/kde-base/kwin-4.7.1-r1/work/kwin-4.7.1/kwin/effects/blur/blur.cpp:33
both crahes are deep down in the driver and out of our control. Ensure that direct rendering is enabled. In the worst case ensure by using KWIN_DIRECT_GL=1. There's nothing we can do in kwin about it. We cannot investigate such issues without experienceing the crashes ourselves. Yes, yes, I understood that. The problem was, that after the first crash with kwin-4.7.1 I switched to OpenGL and kwin crashed very severly upon the first start. I downgraded the driver, KDE started normally, and _then_ I noticed that DR was disabled. I am now on mesa-7.11 and video-intel-2.16.0 with classic drivers and OpenGL, and it works. I simply wanted to have the Backtraces here for the intel devs. ;-) I mark this bug as RESOLVED/WONTFIX (Dunno whether INVALID might be the better choice) |