XServer sometimes hangs (100% CPU) when closing a window on R500/video-ati

Bug #293052 reported by Alexander Hunziker
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Compiz
Fix Released
Medium
compiz (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I've been using compiz on an ATI Mobility Radeon X1400 for a few days now. Using the default driver (video-ati). Sometimes, when trying to close a window, it just hardlocks and won't accept any input anymore (can't switch to terminal, can't kill XServer), though the mouse pointer can still be moved. The only thing that can be done is a cold reboot.

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

I've been using Compiz on R500 on a daily basis now for a few weeks, always using the most recent radeon driver form Tormod Volden's PPA. So far, I have not experienced the described crashes anymore with those more recent drivers.

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

The bug persists. I cannot be sure it has anything to do with Compiz, that was my first guess because it always happens when i close a program. Today though, it happened when I closed a program from the tray icon while the program was minimized to tray - there was no visible window being closed.

It's tough to debug, because it only happens once every week or so, but reproducibly when i close an app. Again, I have no possibility to control the machine locally. The fan speeds up, so I think the CPU is working.

Can anybody give me advice how to debug when it happens next time? I have installed an SSH server now in the hope to login remotely next time it happens.

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

It happened again just now. This time, I logged in remotely and saw that the process "Xorg" was using 100% CPU. I was able to kill it over SSH, after which the X session is shut down and I'm again presented with the login screen.

Can somebody please give me instructions what to do next time it happens in order to debug this? At a rate of once every two weeks, I need to be prepared, or else we'll never get this fixed :-)

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

alexander, thank you for your persistence
i'm no expert here, but you might want to take a look here:
https://wiki.ubuntu.com/X/Debugging
especially:
https://wiki.ubuntu.com/X/Reporting
good luck

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

Attaching Xorg.0.log.old. It contains a lot of messages like:

[mi] EQ overflowing. The server is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event; dropping.

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

Also, my xorg.conf. I'm using:

* The radeon driver 6.10 released very recently. It also happens though with the version released with Intrepid.
* EXA
* Compiz

Revision history for this message
Alexander Hunziker (alex-hunziker) wrote :

It happened again, and i was *so* prepared :-) Here's a backtrace, hope that helps.

Revision history for this message
Janigo (cardi-gmx) wrote :

I can confirm this on openSUSE 11.1 (gnome) on a thinkpad T60 with an radeon X1400 graphics-card. It only happens if compiz is running. Using radeonHD driver, compiz does not work (white screen).

Changed in compiz:
status: Unknown → Confirmed
Changed in compiz:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed in Jaunty.

Changed in compiz (Ubuntu):
status: New → Fix Released
Changed in compiz:
importance: Unknown → Medium
Changed in compiz:
importance: Medium → Unknown
Changed in compiz:
importance: Unknown → Medium
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.