glxinfo crashed with SIGSEGV in XF86DRIQueryExtension()

[Thiago Figueiro]

Opened terminal, typed `glxinfo' followed by `sudo glxinfo'.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mesa-utils 7.7-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sun Apr 4 23:44:34 2010
DkmsStatus: fglrx, 8.721, 2.6.32-19-generic, i686: installed
ExecutablePath: /usr/bin/glxinfo
MachineType: Dell Inc. Inspiron 1501
ProcCmdLine: root=UUID=373e7eb4-f58f-48b6-b6a1-b7a6b55aea49 ro quiet splash
ProcCmdline: glxinfo
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xe76ed6 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x00e76ed6) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mesa
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? ()
 ?? ()
 ?? ()
Title: glxinfo crashed with SIGSEGV in XF86DRIQueryExtension()
UserGroups:

dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0UW744
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 1501
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-19-generic

[Thiago Figueiro (thiagocsf)]

Also, in `dmesg':

[ 182.554496] glxinfo[2257]: segfault at 4 ip 00775ed6 sp bf97b020 error 4 in libGL.so.1.2[710000+a7000]
[ 189.598254] glxinfo[2259]: segfault at 4 ip 00e76ed6 sp bfc3ba80 error 4 in libGL.so.1.2[e11000+a7000]
[ 231.464828] glxinfo[2491]: segfault at 4 ip 00b8ced6 sp bfcac800 error 4 in libGL.so.1.2[b27000+a7000]
[ 958.596858] glxgears[9222]: segfault at 4 ip 008b7ed6 sp bfa57970 error 4 in libGL.so.1.2[852000+a7000]
[ 981.222379] glxgears[9225]: segfault at 4 ip 00429ed6 sp bf93ecf0 error 4 in libGL.so.1.2[3c4000+a7000]
[ 984.186742] glxgears[9227]: segfault at 4 ip 00175ed6 sp bfeb68a0 error 4 in libGL.so.1.2[110000+a7000]
[ 1025.511043] glxgears[9255]: segfault at 4 ip 00535ed6 sp bff90740 error 4 in libGL.so.1.2[4d0000+a7000]

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00e76ed6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x0000000d in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? ()

[emarkay (mrk)]

I also just got an Apport created bug on this. Let me know if any of the data it collected is needed.

[Alberto Milone (albertomilone)]

It looks like you're using the open source driver with the libraries from the proprietary driver.

Can you remove the fglrx package and install the driver from Jockey (the restricted drivers manager), please?

[Thiago Figueiro (thiagocsf)]

Hi, Alberto.

Thanks for that and right you are. I've removed all traces of the proprietary driver and reinstalled the open-source driver. Running glxinfo no longer dumps a core:

$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".

Still doesn't work as it did on 9.10. Should this be handled on a different bug entry?

xorg.conf is pretty standard:

Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "radeon"
EndSection

Cheers

[Robert Hooker (sarvatt)]

He asked you to remove it and then install it through jockey (system - preferences - hardware drivers) because thats what sets up the glx and gl right and your system got into a funky state. After you do that, then you can deactivate the drivers (from jockey again, not apt-get or synaptic!) and the open ones should work right. You dont need that xorg.conf for the open drivers.

[Thiago Figueiro (thiagocsf)]

Jockey doesn't seem to pick-up anything:

thiagof@xingu:~$ jockey-text

Searching for available drivers...
thiagof@xingu:~$

thiagof@xingu:~$ sudo jockey-text -l
firmware:b43 - Broadcom B43 wireless driver (Free, Enabled, In use)
kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use)

Thanks for the help, by the way. Has anyone seen a procedure/howto/thread somewhere and wouldn't mind posting the URL? I feel a bit bad using the bug tracker for "support".

thiagof@xingu:~$ sudo jockey-text --hardware-ids
modalias:pci:v00001002d00005975sv00001028sd000001F5bc03sc00i00
modalias:input:b0019v0000p0003e0000-e0,1,k8E,ramlsfw
modalias:pci:v00001022d00001100sv00000000sd00000000bc06sc00i00
modalias:pci:v00001180d00000822sv00001028sd000001F5bc08sc05i00
modalias:acpi:PNP0000:
modalias:acpi:device:
modalias:pci:v00001002d00005A37sv00000000sd00000000bc06sc04i00
modalias:input:b0019v0000p0005e0000-e0,5,kramlsfw0,
modalias:platform:dcdbas
modalias:usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
modalias:pci:v00001022d00001101sv00000000sd00000000bc06sc00i00
modalias:input:b0019v0000p0000e0000-e0,1,k94,95,A1,E0,E1,EC,EE,1AF,ramlsfw
modalias:acpi:PNP0B00:
modalias:pci:v00001022d00001103sv00000000sd00000000bc06sc00i00
modalias:platform:Fixed MDIO bus
modalias:pci:v00001002d0000438Csv00001028sd000001F5bc01sc01i8a
modalias:platform:regulatory
modalias:pci:v00001180d00000843sv00001028sd000001F5bc08sc80i00
modalias:pci:v00001002d00005950sv00001028sd000001F5bc06sc00i00
modalias:acpi:PNP0C01:
modalias:acpi:PNP0800:
modalias:pci:v00001002d00005A3Fsv00000000sd00000000bc06sc04i00
modalias:acpi:PNP0C02:
modalias:acpi:LNXTHERM:
modalias:acpi:LNXSYSTM:
modalias:acpi:PNP0303:
modalias:ssb:v4243id0807rev03
modalias:pci:v00001002d00004380sv00001028sd000001F5bc01sc06i01
modalias:pci:v000014E4d0000170Csv00001028sd000001F5bc02sc00i00
modalias:input:b0017v0001p0001e0100-e0,1,2,k110,111,112,r0,1,amlsfw
modalias:input:b0000v0000p0000e0000-e0,5,kramlsfw4,
modalias:input:b0011v0002p0007e01B1-e0,1,3,k110,111,112,145,14A,14D,14E,ra0,1,18,1C,mlsfw
modalias:ssb:v4243id0806rev07
modalias:pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00
modalias:dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
modalias:acpi:PNP0100:
modalias:ssb:v4243id0817rev03
modalias:input:b0019v0000p0006e0000-e0,1,kE0,E1,E3,F0,F1,F2,F3,F4,F5,ramlsfw
modalias:usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
modalias:pci:v00001022d00001102sv00000000sd00000000bc06sc00i00
modalias:acpi:SYN1015:SYN0100:SYN0002:PNP0F13:
modalias:acpi:LNXSYBUS:
modalias:pci:v00001002d00004384sv00000000sd00000000bc06sc04i01
modalias:pci:v00001002d00005A38sv00000000sd00000000bc06sc04i00
modalias:pci:v00001002d0000438Dsv00001028sd000001F5bc06sc01i00
modalias:pci:v00001002d00004386sv00001028sd000001F5bc0Csc03i20
modalias:platform:pcspkr
modalias:input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8D,8E,8F,94,98,9B,9C,9D,9E,9F,A2,A3,A4,A5,A6,AC,AD,B7,B8,B9,BF,C1,CD,D4,D7,D9,E0,E1,E2,E3,EC,EE,ram4,l0,1,2,sfw
modalias:acpi:PNP0200:
modalias:pci:v00001002d00004385sv00001028sd000001F5bc0Csc05i00
modali...

[Felix Kuehling (felix-kuehling)]

Hi Thiago,

your hardware is not supported by the fglrx driver. Only R6xx and later hardware is supported by the current driver version. The problem is that you're using the radeon driver while fglrx is installed. The fglrx libGL and libglx is incompatible with the radeon driver. Uninstall fglrx and the radeon driver should work correctly.

[Thiago Figueiro (thiagocsf)]

Thanks all. I was going to mark this bug as invalid but other people have marked the bug as affecting them. I'll let it sit for a while but afaic this can be closed.

[Pedric (pedric)]

Using a laptop with hybrid graphics (integrated intel & dedicated amd gpu), this bug hits me while running in integrated mode. I am using a hybrid xorg.conf that uses either gpu if activated in bios. For me, the fglrx driver is unfortunately required for proper load-dependent (dynamic) frequency scaling of the dedicated GPU without flickering at frequency changes. With the intel driver running, libgl crashes every time it is used...

[Pedric (pedric)]

I found that you don't need uninstall fglrx (or nvidia, as that driver will ship its own libGL as well) to use mesa libGL again - you can use

sudo update-alternative --set gl_conf /path/to/ld.so.conf

To see the available GL configurations, run

update-alternatives --list gl_conf

For example, if you run one of the open source drivers such as intel, radeon or nouveau, update the gl configuration alternative to the mesa configuration.

sudo update-alternative --set gl_conf/usr/lib/mesa/ld.so.conf

Or, if you run fglrx run

sudo update-alternative --set gl_conf /usr/lib/fglrx/ld.so.conf

Nvidia ships its own GL configuration alternative, which works the same. After doing so, you need to run

sudo ldconfig

to reconfigure the dynamic linker run-time bindings. It may be better to do so when X is not running, as e.g. fglrx will crash if you switch to mesa while it is running.

[Andrey Zhidenkov (agwts)]

I have the same problem. I got this error, when I've installed fglrx driver via apt-get on Ubuntu 11.04 beta 2. When I reboot, Unity reports error and doesn't start. glxgears crashed. So how can I have this driver worked correctly?

[ski (skibrianski)]

Thanks a lot Pedric - that worked for me. I can run google-chrome (which I am hopelessly addicted to), and various other programs don't crash/spam dmesg randomly.