[RV370] system freeze with 3D screensaver

Bug #946822 reported by Tpugliese on 2012-03-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)

Bug Description

Running any of the 3D screensavers results in a complete system freeze. The PC is unresponsive and must be powered down to recover. The "Surfaces" screensaver seems to reproduce the problem the quickest. It will usually hang in under a minute. I reported this issue with 11.10 here https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/933921 After upgrading to 12.04, the hang is still present.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686

ApportVersion: 1.94-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Mar 4 21:07:47 2012
DistUpgraded: Log time: 2012-02-19 12:37:26.420062
DistroCodename: precise
DistroVariant: ubuntu
 virtualbox, 4.1.8, 3.2.0-17-generic, i686: installed
 virtualbox, 4.1.8, 3.2.0-17-generic-pae, i686: installed
 virtualbox, 4.1.8, 3.2.8, i686: installed
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
 Advanced Micro Devices [AMD] nee ATI RV370 5B64 [FireGL V3100 (PCIE)] [1002:5b64] (rev 80) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices [AMD] nee ATI Device [1002:0102]
   Subsystem: Advanced Micro Devices [AMD] nee ATI Device [1002:0103]
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Precision WorkStation 380
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic-pae root=UUID=54c8772a-62f1-4edb-8bb1-b671d6f8deac ro vga=769 quiet splash radeon.modeset=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to precise on 2012-02-19 (14 days ago)
dmi.bios.date: 04/18/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0CJ774
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2006:svnDellInc.:pnPrecisionWorkStation380:pvr:rvnDellInc.:rn0CJ774:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation 380
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

Tpugliese (thomas-pugliese) wrote :
Timo Aaltonen (tjaalton) on 2012-03-05
affects: xorg (Ubuntu) → mesa (Ubuntu)
Bryce Harrington (bryce) wrote :

No errors in any of the log files.

If you move aside your /etc/X11/xorg.conf are you still able to reproduce the freeze?

When the system is frozen, can you ssh into the computer? If so, please collect 'sudo dmesg > dmesg.txt' and your /var/log/kern.log and attach to this bug report.

Also, which screensaver package are you using? The 3D screensavers were removed from the version of GNOME included in 12.04; are you using xscreensaver?

summary: - system freeze with 3D screensaver
+ [RV370] system freeze with 3D screensaver
Changed in mesa (Ubuntu):
status: New → Incomplete
Tpugliese (thomas-pugliese) wrote :

The freeze still happens with no xorg.conf file.

After the freeze, I can't ssh into the host.

Yes, I am using xscreensaver with xfce.

Bryce Harrington (bryce) wrote :

If you cannot ssh into the machine at all then likely your bug is something deeper than just X. Could be a kernel OOPS for example. You may need to do some additional diagnosis to find out what exactly broke.

However, on the off chance it is indeed a bug in mesa, I've put the new 8.0.3 version of mesa in a PPA for you to test. This has a collection of various important bugfixs. Since you have not discovered an error message, there's no way to know whether this 8.0.3 update is relevant for you issue except to just test it, so add the PPA, upgrade to that version, and retest. Let us know one way or the other if the issue goes away after rebooting with this installed.


Changed in mesa (Ubuntu):
status: Incomplete → New
status: New → Incomplete
bugbot (bugbot) wrote :

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

Changed in mesa (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers