[RV570] x11 crashes durring screensaver

[Tom]

When my system goes to screensaver x11 crashes, but not every time.

Current system:
Ubuntu 8.10 (gnome)
Dell optiplex 745
Graphics Card: ATI Radeon x1950 pro
Dual Screen Monitors

Common applications I run are:
Eclipse (ganymede)
  - I build and run an java application using swing, and jogl.
Firefox 3.0.4
Evolution
Amarok
Gnome Terminal
gedit
Screensaver - Euphoria

I've attached a copy of my xorg log.

When the crash occurs I can only restart my x server by restarting my computer. Also after the crash occurs my computer ends up on a display that looks like the system is starting up, but it does not make it to the login screen. I am able to switch to a different virtual login, but not able to restart the x server. This problem probably occurs about every 10-15 times it goes to screensaver.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory Controller Hub [8086:2990] (rev 02)
     Subsystem: Dell Device [1028:01da]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV570 [Radeon X1950 Pro] [1002:7280]
     Subsystem: ATI Technologies Inc Device [1002:0b12]

[Tom (gomp3x)]

Additional information:
Once the x server crashes and it looks like the system is booting this is what it says:
...
* Not starting GNOME Display Manager (gdm); it is not the default display manager.
Starting K Display Manager: kdm.
...

I am running GNOME.

[Timo Aaltonen (tjaalton)]

no need to keep open for xorg.

[Tom (gomp3x)]

I changed my display manager to gdm and it still crashes. The only difference when it crashes it brings me to the login screen, and I don't need to restart my computer, just login in again.

[Bryce Harrington (bryce)]

[This is an automated message]

Hi gomp3x,

Please attach the output of `lspci -vvnn` too.

[Tom (gomp3x)]

Here are the result of the lspci -vvnn command.

[Tom (gomp3x)]

I have an idea why this may be occurring and it might be related to a problem I get with audio in ubuntu 8.10.

First the problem that I get with audio is when multiple applications try to use audio, one after the other, or at the same time they more often than not get locked in a futex_wait and freeze. The only way for me to fix this problem is to kill (not end because that doesn't work) all of the processes that are in the futex_wait. Then I can restart the application I want to listen to audio on and it will work until the problem occurs again and I have to redo the process. An example of this is if I watch something on youtube (firefox) then play a song using Amarok then watch something on youtube, firefox will freeze up and be in a futex_wait state. And if I try to then play a song with Amarok it will freeze and be in a futex_wait. I have to kill all the processes that in a futex_wait before I can use one of them to listen to audio.

But the reason this may relate to my problem of the display manager crashing is because my screen saver is a 3d screen saver and for some reason 3d application make noise (use the audio driver). So what I'm guessing is gdm gets into a futex_wait which causes a freeze/crash because the 3d screen saver is making noise (using the audio driver).

So I guess there are two problems here:
1. The problem with when multiple application use audio the applications end up in the futex_wait state and freeze.
2. The problem that 3d applications make noise (use the audio drivers) when they are no suppose to.

[Tom (gomp3x)]

Just thought I would let everyone know that this was never fixed for Ubuntu 8.10, but there is now a newer version of Ubuntu, 9.04.

I hope this problem doesn't continue with the newer version.

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.