[needs EXA] - x-server crash with compiz using ati X300

Bug #227936 reported by Sam_
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Hi,
I do what Bryce said in Bug #108527
>>This is why we so strongly encourage each person to report their issue separately.<<

Random crashes once every hour. Compiz enabled with Normal not Extra.
I've already removed all .xml files in gconf/apps and restarted to generate them new.

System: amd_64 Hardy 8.04
Packages:
#xserver-xorg 1:7.3+10ubuntu
#xserver-xorg-v 1:6.8.0-1 X.Org X server -- ATI display driver
#compiz 1:0.7.4-0ubunt
uname: Linux myname 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

Output from Terminal:
#compiz.real --replace; compiz
compiz.real (core) - Fatal: GLX_EXT_texture_from_pixmap is missing
compiz.real (core) - Error: Failed to manage screen: 0
compiz.real (core) - Fatal: No manageable screens found on display :0.0
Checking for Xgl: not present.
Detected PCI ID for VGA: 05:00.0 0300: 1002:5b60 (prog-if 00 [VGA controller])
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Comparing resolution (1024x768) to maximum 3D texture size (2048): Passed.
Checking for nVidia: not present.
Checking for FBConfig: present.
Checking for Xgl: not present.
Starting gtk-window-decorator
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format
GConf backend: There is an unsupported value at path /apps/compiz/plugins/scale/allscreens/options/initiate_edge. Settings from this path won't be read. Try to remove that value so that operation can continue properly.

I've set the option initiate_edge back in the gconf-editor, it was looking like that [] empty and after setting back the [] disappeard, after reboot compiz was deactivated and [] was there again.

I know that X300 ist blacklisted in the usr/bin/compiz:
# blacklist based on the pci ids
# See http://wiki.compiz-fusion.org/Hardware/Blacklist for details
T=" 1002:5954 1002:5854 1002:5955" # ati rs480
T="$T 1002:4153" # ATI Rv350
T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965
T="$T 8086:2972" # i965 (x3000)
T="$T 1002:3152 1002:3150 1002:5462 1002:5653 " # ati X300 X600,X600 X700
BLACKLIST_PCIIDS="$T"
unset T

#glxinfo
direct rendering: Yes

#xorg.conf
Section "Device"
 Identifier "ATI Technologies, Inc. RV370 5B60 [Radeon X300 (PCIE)]"
 Driver "ati"
 BusID "PCI:5:0:0"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI Technologies, Inc. RV370 5B60 [Radeon X300 (PCIE)]"
 Monitor "SDM-X52"
 DefaultDepth 24

My question is, if I will be forced to buy a different graphic card, because some effects from compiz are healthy for my eyes, like zooming and transparency.

I'm not able to trace from another machine, but attache the Xorg.log.
I'd be happy to provide any information needed for resolving the issue. Thanks.

Revision history for this message
Sam_ (and-sam) wrote :
Sam_ (and-sam)
description: updated
Revision history for this message
Sam_ (and-sam) wrote :

Hi,
after booting today Compiz was deactivated. I activated and had after about half an hour freeze, only the Mouse can be moved. When trying to restart X with strg+alt+back the mouse immediately freezes also, then nothing helps but strg+alt+Sysq. (This procedure takes place every freeze)
The last message in Xorg.0.log is (II) XAA: Evicting pixmaps.

Revision history for this message
Sam_ (and-sam) wrote :

I should add, yesterday I'd started compiz in the terminal, before shutdown I closed the terminal. No else messages were add in the output which is posted above.
In about five hours after starting compiz in the terminal no freeze, that was after I've removed all the .xml files. I've triggered by opening flash, totem and other apps.
After rebooting today since the last freeze I had no freeze since 90 minutes. I will trigger now again by opening different apps and report later.

Revision history for this message
Sam_ (and-sam) wrote :

Hi,
ok I give up, had two crashes about every hour. The last one 10 minutes ago and interesting on this one was, that while watching a stream with vlc (totem before had a segfault while playing a youtube video), I wanted to close the playlist window, nothing happened.
I could still move the mouse and hear the stream. No shortcuts help so I did again strg+alt+sysq.
After reboot compiz was still activated and the mouse was kind of wobbling, I deactivated and switch now to metacity, which I've never had a crash with.

Revision history for this message
Sam_ (and-sam) wrote :

Hi,
since I've read all the filed bugs #108527 + #195051 and some include option settings, I attach my xorg.conf, because it didn't change since Jan.07
Maybe I just miss some settings, because I didn't have compiz.real at this time of course.
Would be kind if someone could take a look and maybe has a hint for me. Thanks.

Revision history for this message
Sam_ (and-sam) wrote :

Update:
since I have a new monitor I attach the new Xorg.0.log, crashes remain. (The xorg.conf didn't change after installing the new monitor, everything was automatically recognized without any problems, great work btw.)

But according to the testing script from here
http://forlong.blogage.de/article/pages/Compiz-Check
Compiz should work fine, this is of course confusing.

#chmod +x compiz-check
#./compiz-check
Gathering information about your system...

 Distribution: Ubuntu 8.04
 Desktop environment: GNOME
 Graphics chip: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
 Driver in use: radeon
 Rendering method: AIGLX

Checking if it's possible to run Compiz on your system...

 Checking for texture_from_pixmap... [ OK ]
 Checking for non power of two support... [ OK ]
 Checking for composite extension... [ OK ]
 Checking for FBConfig... [ OK ]
 Checking for hardware/setup problems... [ OK ]

Revision history for this message
Sam_ (and-sam) wrote :

Update:
Good news, since three days I've added in the xorg.conf to device section
Option "AccelMethod" "EXA"
and had no crash using compiz.real

Revision history for this message
Sam_ (and-sam) wrote :

Hi,
since I received this message:
[** Changed in: xorg (Ubuntu)
Sourcepackagename: None => xorg]
I provide the package description again:
xorg 1:7.3+10ubuntu10 X.Org X Window System

Still no crash since eleven days now and this only by adding one option in the xorg.conf
For the record, the new configuration relating to the new monitor ( see last Xorg.0.log) does not appear in the xorg.conf e.g. other modelines, Ubuntu configures wherever automatically, how amazing.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for reporting this bug to help make Ubuntu better, unfortunately there's not enough information to troubleshoot it. You mention that this bug results in an Xorg crash if you aren't specifying EXA in xorg.conf; does this crash still occur on Hardy? If so, could you please collect a full backtrace (see http://wiki.ubuntu.com/X/Backtracing for directions).

Changed in xorg:
status: New → Incomplete
Revision history for this message
Sam_ (and-sam) wrote :

Hi Bryce,
thanks a lot for the reply.
As mentioned in the entry the crash has happened with System: amd_64 Hardy 8.04
Since adding the "EXA option" in my xorg.conf, crashes are gone, and it looks like for good.

So my guess, it has nothing to do with the open driver, it has something to do with Xorg on one hand, on the other hand not directly, because I've read somewhere the "EXA option" is available, but not as default, as one can see in my last Xorg.0.log the EXA modules are being loaded without downloading any further packages or changing configurations by also running a default configurated system, means no changes in systemfiles.
So when only by adding this option the problem is solved here, this seems for me, the driver is ok, xorg is ok, the options which are available can be activated or not, means one can configure the system easily, one only has to know how and reading bug files, since there appears no popup telling one what option to add and how to do that.

package: xorg 1:7.3+10ubuntu10 X.Org X Window System

Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, well we'll be switching to EXA by default at some point for -ati, so the bug could be closed at that point.

Fwiw, generally even XAA/EXA issues can be driver bugs since most of the code for implementing those two acceleration articles lives within that driver.

Changed in xserver-xorg-video-ati:
importance: Undecided → High
status: Incomplete → Triaged
Revision history for this message
Brian Murray (brian-murray) wrote : Ubuntu needs you!

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

Changed in xserver-xorg-video-ati:
status: Triaged → Incomplete
Revision history for this message
Sam_ (and-sam) wrote : Re: needs EXA - x-server crash with compiz using ati X300

Hi Brian,
thanks for the confidence, but I wouldn't consider me as a user with moderate skills in linux, as recommended on testuser wiki.
However, I've downloaded the .iso file, burned it, checked it, left it inside and restarted, but it didn't boot with the Live CD and without distress I'll not mess with my BIOS settings, since I'm working on a single productive system which is functioning well since Edgy.
I've to apologize for that.

Revision history for this message
Brian Murray (brian-murray) wrote :

When booting your system and the BIOS is running / loading on most systems you can press "F2" or "F12" to access a one-time boot menu. This will allow you to boot from the CD drive just once and you won't have to go into the actual BIOS menu and risk harming anything.

Revision history for this message
Sam_ (and-sam) wrote :

No success with F2, F12, F6.

Revision history for this message
Sam_ (and-sam) wrote :

Hi Brian,
success with F11, attach Xorg.0.log and xsession.errors right away.
Compiz was enabled "Normal", cube or other plugins are obviously not available.
Only two workspaces can be activated.

Revision history for this message
Sam_ (and-sam) wrote :
Changed in xserver-xorg-video-ati:
status: Incomplete → Triaged
Revision history for this message
Sam_ (and-sam) wrote :

Hi again,
while I was supposed to make another test (#184907 and it happened #251910, but put these aside), regarding this bug here I had to boot the LiveCD twice since every time I had to turn off the machine because of a complete freeze, none of the common rescue key short cuts worked, mouse was moveable.
It just happens sporadicly when opening a menu in Totem or Firefox. In example the first session when the freeze occured with Totem the workspace switcher disappeared also from the panel.
I suppose this doesn't help you very much because I can't provide any logs from the Live CD sessions and have no idea if it has something to do with compiz or the driver, sorry.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-ati - 1:6.9.0+git20081003.f9826a56-0ubuntu6

---------------
xserver-xorg-video-ati (1:6.9.0+git20081003.f9826a56-0ubuntu6) jaunty; urgency=low

  * Add 104_use_exa.patch: Switches to EXA acceleration by default.
    + See https://wiki.ubuntu.com/X/Blueprints/RadeonXaaToExa
    + Should close the following bugs (please reopen if not):
      LP: #227936, #269357, 68224 110384 132707

 -- Bryce Harrington <email address hidden> Fri, 19 Dec 2008 19:46:27 -0800

Changed in xserver-xorg-video-ati:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.