Bug 69682 - mesa-9.2.0 and glamor-0.5.1 crash X - (?) _mesa_GetVertexAttribdv (?)
Summary: mesa-9.2.0 and glamor-0.5.1 crash X - (?) _mesa_GetVertexAttribdv (?)
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 9.2
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
: 66359 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-09-22 20:39 UTC by Denis M. (Phr33d0m)
Modified: 2018-03-08 05:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
X-crash-backtrace.txt (11.43 KB, text/plain)
2013-09-22 20:40 UTC, Denis M. (Phr33d0m)
Details
xorg.conf (2.12 KB, text/plain)
2013-09-23 06:59 UTC, Denis M. (Phr33d0m)
Details

Description Denis M. (Phr33d0m) 2013-09-22 20:39:04 UTC
Hello, 

First of all, please change the summary to something better as I had no idea how to describe this issue.

So, I switched to the radeon driver and I'm trying to use glamor. The backtrace is reproducible always if I add: `Load "glamoregl"` to my xorg.conf

If I don't load the glamoregl it fallbacks to swrast.
Comment 1 Denis M. (Phr33d0m) 2013-09-22 20:40:36 UTC
Created attachment 86329 [details]
X-crash-backtrace.txt
Comment 2 Ian Romanick 2013-09-22 23:27:22 UTC
This is the same underlying issue as bug #66359 and probably others.  The fundamental problem is that glamor is doing something that can never work: linking with libGL in the xserver.  libGL and the xserver's GLX module fight about where functions go in the dispatch table, and everybody loses.

*** This bug has been marked as a duplicate of bug 66359 ***
Comment 3 Marek Olšák 2013-09-22 23:35:45 UTC
(In reply to comment #2)
> This is the same underlying issue as bug #66359 and probably others.  The
> fundamental problem is that glamor is doing something that can never work:
> linking with libGL in the xserver.  libGL and the xserver's GLX module fight
> about where functions go in the dispatch table, and everybody loses.
> 
> *** This bug has been marked as a duplicate of bug 66359 ***

Are you suggesting that Glamor is doomed to never work reliably for everybody, and that the X.Org state tracker (Gallium driver + DDX->Gallium translation layer) providing a complete DDX in one .so is the way to go for Mesa drivers without a DDX?
Comment 4 Marek Olšák 2013-09-22 23:36:51 UTC
Sorry for reopening. Anyway, Denis, please attach your xorg.conf. I think this can be fixed at least for you.
Comment 5 Kenneth Graunke 2013-09-23 03:56:42 UTC
ajax is talking about things related to this at XDC this year.  There are definitely solutions.
Comment 6 Denis M. (Phr33d0m) 2013-09-23 06:59:52 UTC
Created attachment 86334 [details]
xorg.conf

(In reply to comment #4)
> Sorry for reopening. Anyway, Denis, please attach your xorg.conf. I think
> this can be fixed at least for you.
Thanks in advance for your time, Marek.

Here's what my xorg.conf looked like when I submitted this bug. After you guys said that glx is fighting with glamor I commented out the "Load glx" part and uncommented "Load glamoregl" and finally KDE booted fine.

The problem before was that some of my KDE effects didn't work because "they needed OpenGL" where OpenGL was available (glxgears ran just fine) and the desktop experience was fluid.

This is what I had:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 256 bits)
OpenGL version string: 2.1 Mesa 9.2.0
OpenGL shading language version string: 1.30

The problem now is that (effects work but) the desktop is very very laggy and there's lot of corruption here and there (the corruption seems smaller with OpenGL 2.0 selected in KDE's settings, with 1.2 and 3.1 there's much more).

This is what I have now:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN
OpenGL version string: 2.1 Mesa 9.2.0
OpenGL shading language version string: 1.30


Marek Olšák, I hope you have some more tricks for my xorg.conf other than the gfx/glamoregl ones!
Comment 7 Marek Olšák 2013-09-23 10:47:42 UTC
Sorry, I don't have any other tricks. I only knew that Load "glx" must not be present in xorg.conf for Glamor to work.
Comment 8 Michel Dänzer 2013-09-25 16:39:19 UTC
This was a configuration error (loading the "glx" module before the "glamoregl" one).

(And yes, I'm aware of the issues with the way glamor currently handles GL dispatch, but apparently Adam Jackson and Eric Anholt will be working on improving that, and in the meantime there is no point in loading the "glx" module manually anyway)
Comment 9 Timothy Arceri 2018-03-08 05:07:39 UTC
*** Bug 66359 has been marked as a duplicate of this bug. ***


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.