Summary: | GLAMOR:X crashes when clicking the OpenGL entry in KInfoCenter | ||
---|---|---|---|
Product: | xorg | Reporter: | thepouar |
Component: | Server/Acceleration/glamor | Assignee: | Alex Deucher <alexdeucher> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | nrndda, thepouar, zhigang.gong |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Is this still an issue with a newer glamor version? yes, And in Mesa 10.1-rc I think this is a duplicate of bug 71190 Could you test with current git master branch. This patch [1] should help. [1] http://cgit.freedesktop.org/xorg/driver/glamor/commit/?id=073c97f494ffe67b15b7a6a95fa894c3e109d862 nope still there. I assume the display manager (currently using KDM) is suppose to restart the X server after a crash right? Created attachment 93880 [details]
Xorg.0.log right after crash
(In reply to comment #5) > Created attachment 93880 [details] > Xorg.0.log right after crash Are you sure that you get this with the commit mentioned above? Because the error message "destination is framebuffer incomplete" has been removed with that patch. <snip> - FatalError("destination is framebuffer incomplete: %s [%x]\n", - str, status); + glamor_fallback("glamor: Failed to create fbo, %s\n", str); + err = -1; <snip> Created attachment 93884 [details]
Xorg.0.log right after crash (right one this time)
oops, wrong log.
(In reply to comment #7) > Created attachment 93884 [details] > Xorg.0.log right after crash (right one this time) > > oops, wrong log. There is no glamor symbol in this log. Could you possible to get a gdb back trace or build glamor with debug symbol then get a new log? Thanks. Created attachment 93931 [details]
Xorg.0.log with -g
here ya go
(In reply to comment #7) > Created attachment 93884 [details] > Xorg.0.log right after crash (right one this time) > > oops, wrong log. The root cause may be: [ 1230.077] XXX fail to create fbo. Which means a glamor_egl_create_textured_pixmap() failed to set a texture to a pixmap. This is an unexpected situation. As the texture is created from an image which already allocated on the gpu memory, this call should not fail. Maybe we need to change the logmessage to an assertion. This bug should be related to the ATI driver. The key hint here is to investigate how the function glamor_set_pixmap_texture() which is called in glamor_egl_create_texture_pixmap() fail to ensure the texture to a fbo. I have zero experience programming drivers, much less debugging. I probably wouldn't know what to look for. Alex, I believe this should be a driver related bug. You may want to take a look. Created attachment 94596 [details]
Backtrace from xorg after a try to open OpenGL tab in Kinfocenter
I have the same bug. Maybe this backtrace will help.
Created attachment 94599 [details]
Another backtrace after building mesa with debug symbols.
When building galmor, xorg-server, xf86-video-ati, glibc and mesa with CFLAGS="-O0 -pipe -ggdb -g -Wall" xserver doesn't crash but just freezes and in gdb produces this backtrace.
Lots of changes to glamor in the last 3+ years, please reopen if you still see this with current releases. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 89930 [details] Xorg log file X crashes when clicking the OpenGL entry in KInfoCenter when using GLAMOR. It works just fine with EXA. I'm using Radeon 6970.