Bug 36318 - r600g segfaults
Summary: r600g segfaults
Status: RESOLVED DUPLICATE of bug 36282
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2011-04-16 22:52 UTC by Ian Milligan
Modified: 2011-04-20 08:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Ian Milligan 2011-04-16 22:52:38 UTC
r600g segfaults running glxgears. Here is a backtrace

#0  0x00007ffff5327f6e in loopback_VertexAttrib3svNV (index=1283, v=0x1e08) at main/api_loopback.c:1137
#1  0x00007ffff532800f in loopback_VertexAttribs3svNV (index=<value optimized out>, n=<value optimized out>, v=0x2dd) at main/api_loopback.c:1220
#2  0x00007ffff525eed6 in execute_list (ctx=0xb55960, list=<value optimized out>) at main/dlist.c:8163
#3  0x00007ffff526130a in _mesa_CallList (list=1) at main/dlist.c:8511
#4  0x0000000000401ce2 in draw ()
#5  0x00000000004035c9 in main ()
Comment 1 Marek Olšák 2011-04-16 23:37:38 UTC
Try 'make clean'.
Comment 2 Yannick Dirou 2011-04-17 02:28:10 UTC
I had similar problem (with r300g) ,

In fact glxgears did not load the right mesa lib
despite a good ldconfig -v (added new mesa path 000_mesa.conf)

ldd /usr/bin/glxgears
it should show the path of the lib used by the app
if it is wrong and you use natty or another ubuntu
a temporary fix is:

sudo rm /etc/ld.so.conf.d/GL.conf (symbolic link to original mesa)
sudo ldconfig

don't know the right fix though
Comment 3 Alexandre Demers 2011-04-17 09:22:02 UTC
If ldd confirms you are using the good library, have a look at the following bug:

It may explain the problem. Otherwise, watchout for Natty, things are a real mess because drivers are now installed under the multiarch folder, but the dev files are installed in a different folder. So if you just compiled and installed like you were doing in previous Ubuntu version, you will end up in a dead end. I had to work a bit to figure everything out.
Comment 4 Ian Milligan 2011-04-18 07:33:20 UTC
Interesting, I'm using LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH I don't think that is the problem. It's only glxgears having this problem, however, so that problem may be with it.
Comment 5 Marek Olšák 2011-04-20 08:43:10 UTC

*** This bug has been marked as a duplicate of bug 36282 ***

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.