Bug 15913

Summary: Hard freeze on launch of glxgears and every other 3D related application
Product: xorg Reporter: Stef <stefan_wb>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high    
Version: 7.3 (2007.09)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.log crash protocol none

Description Stef 2008-05-12 16:10:03 UTC 
Created attachment 16492 [details] [review]
Xorg.log crash protocol

I'm having a total lockup after starting glxgears. I'm only able to reboot after that. The glxgears window appears but stays black.

I'm running:
libgl 7.0.3rc2-1
mesa 7.0.3rc2-1
xf86-video-ati 6.8.0-2
xorg-server 1.4.0.90-9

I thought that this might be an kernel related issue. I tried an knoppix dvd with kernel 2.6.19.5 and glxgears ran succesfully. The i compiled 2.6.19.7 on my arch with the config from knoppix. But then i experienced the same issue. Still a hard freeze on glxgears.
So this is not kernel related i think.

I saw this bug with Archlinux and Ubuntu (Hardy). With every other opengl related application the same problem.

There was a workaround. I ran glxgears as root and it was ok. After that i could run glxgears normaly as regular user till next boot. But that was just  working in gnome with gnome terminal. In Fvwm with xterm i had also as root a crash.

In the attachement is the Xorg.log after a glxgears crash.

Here is my xorg.conf:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection

Section "Module"
Load "dbe"
Load "xtrap"
Load "dri"
Load "glx"
Load "extmod"
Load "record"
Load "GLcore"
Load "freetype"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize 340 270 # mm
Identifier "Monitor0"
VendorName "ACR"
ModelName "Acer AL1721"
### Comment all HorizSync and VertRefresh values to use DDC:
HorizSync 30.0 - 83.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "Radeon RV100 QY [Radeon 7000/VE]"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Comment 1 Alex Deucher 2008-05-12 16:18:04 UTC 
Do either of these options help?

Option "BusType" "PCI"
Option "AGPMode" "1"
Comment 2 Stef 2008-05-12 16:37:16 UTC 
Thats so cool. And so quick!!!!!!

That solved it for me.

Should I mark it as fixed or is this still a buggy behaviour and just a workaround (but a very fine one)?
Comment 3 Alex Deucher 2008-05-13 05:32:30 UTC 
(In reply to comment #2)
> Thats so cool. And so quick!!!!!!
> 
> That solved it for me.

which option fixed it?
Comment 4 Stef 2008-05-14 03:24:27 UTC 
Both of them worked by itself.
I'm now running with AGP mode forced to 1x.
Comment 5 Alex Deucher 2008-05-14 05:40:59 UTC 
AGP sucks.
Comment 6 Stef 2008-05-15 04:18:09 UTC 
Can you tell me why this is not a bug. Was it necessary to set these Options?
Comment 7 Alex Deucher 2008-05-15 17:22:58 UTC 
(In reply to comment #6)
> Can you tell me why this is not a bug. Was it necessary to set these Options?
> 

Unfortunately, due to the nature of AGP, it's almost impossible to know the correct safe settings.  Some card/chipset combos only work in 1x mode; others only work in 4x or 8x.  We've gone back and forth in the driver as to the default agp mode.  Unfortunately, no one setting seems to work everywhere.
Comment 8 Michel Dänzer 2008-05-16 01:34:17 UTC 
I think this is the more correct resolution... it is a bug (somewhere), but not one we can realistically fix.

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.