Ubuntu
xserver-xorg-video-ati package

System crashes with open-source radeon driver

Bug #1174042 reported by Lars Kumbier on 2013-04-28

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-ati (Ubuntu)	Invalid	Low	Unassigned

Bug Description

I have a Dell StudioXPS 1640 with an ATI Radeon HD 3670. Unter Ubuntu 12.04, I was able to use the proprietary fglrx driver. However, since the new xserver-xorg introduced in Ubuntu 12.10, I am unable to use the proprietary driver anymore, because ATI stopped support for the graphics card in the newer fglrx-versions compatible with the new xserver.

I now upgraded to Ubuntu 13.04 and tried to get the radeon open-source driver to work. When I activate the driver by installing the xserver-xorg-video-radeon package, the monitor goes dark, flickers once a few seconds later and the system does not react anymore - the only thing still working is the poweroff button. I did try several custom xorg.conf files (minimalistic copy of the fallback with the radeon driver specified, the same with deactivated acceleration and a bigger one with specific screen modes, etc) and the dbus version without any xorg.conf file - all with the same result.

The vesa-driver is unable to detect my monitor correctly and leaves me with 1440x960, which is bad for my monitor, because it is not my native resolution and fuzzy.

I'm now stuck with a generic kernel-mode setting, which has my native resolution, but is sluggish and unusable.

I do not want to be stuck with Ubuntu 12.04 and an unsupported fglrx driver for the next year or so (until I get a new laptop). Any hints and help greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Apr 28 21:17:51 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI RV635/M86 [Mobility Radeon HD 3670] [1002:9593] (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0272]
InstallationDate: Installed on 2013-04-28 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Dell Inc. Studio XPS 1640
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=2cb61677-1194-4d21-8e34-833dcbf89dd3 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0W497D
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2009:svnDellInc.:pnStudioXPS1640:pvrA123:rvnDellInc.:rn0W497D:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Studio XPS 1640
dmi.product.version: A123
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1

Tags:

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-04-28:

BootDmesg.txt Edit (69.4 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (1.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.1 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (43.3 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (2.2 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (7.2 KiB, text/plain; charset="utf-8")
LightdmGreeterLogOld.txt Edit (7.5 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (3.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (16.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.5 KiB, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (176.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (392.9 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (684 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (78.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (111.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.2 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (25.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2013-04-28:

do you still have fglrx installed?

affects:	xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Changed in xserver-xorg-video-ati (Ubuntu):
status:	New → Incomplete

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-04-29:

Sorry for the incorrect information - I've installed 13.04 fresh and did *not* do an upgrade as stated. Therefore, no fglrx was installed. I did perform the steps presented in the wiki to switch from fglrx to the radeon driver anyways and several times like so:

  sudo apt-get remove --purge xorg-driver-fglrx fglrx*
  sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
  sudo dpkg-reconfigure xserver-xorg
  sudo apt-get install --reinstall xserver-xorg-core

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-04-30:

Xorg.log with enabled Radeon Driver Edit (61.8 KiB, text/plain)

I just saw that the Xorg.log-file is still from the Kernel Mode Setting - here is the one with the activated Radeon-Driver, showing an EQ overflow. I've also made an upstream-bugreport at xorg: https://bugs.freedesktop.org/show_bug.cgi?id=64072

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-04-30:

dmesg.log Edit (78.1 KiB, text/plain)

Here's a dmesg from an ssh-session of a normal bootup with a resulting crash. It shows a possible regression to bug #1058303.

tags:

added: regression-update

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-01:

Download full text (3.4 KiB)

Exactly the same problem here (XPS 1640) on a fresh install (livecd boot without problem, but as soon the system is installed on the disk, it doesn't boot...) I have a dark screen instead on the login screen. In dmesg, we can see this :

Apr 28 16:24:18 mat-laptop kernel: [ 35.584061] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
Apr 28 16:24:18 mat-laptop kernel: [ 35.584069] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001)
Apr 28 16:24:18 mat-laptop kernel: [ 35.585105] radeon 0000:01:00.0: Saved 89 dwords of commands on ring 0.
Apr 28 16:24:18 mat-laptop kernel: [ 35.585108] radeon 0000:01:00.0: GPU softreset: 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [ 35.745021] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA0003030
Apr 28 16:24:18 mat-laptop kernel: [ 35.745024] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [ 35.745026] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200200C0
Apr 28 16:24:18 mat-laptop kernel: [ 35.745029] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [ 35.745031] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [ 35.745033] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000800
Apr 28 16:24:18 mat-laptop kernel: [ 35.745036] radeon 0000:01:00.0: R_008680_CP_STAT = 0x800000C1
Apr 28 16:24:18 mat-laptop kernel: [ 35.745038] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE
Apr 28 16:24:18 mat-laptop kernel: [ 35.759919] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
Apr 28 16:24:18 mat-laptop kernel: [ 35.774806] radeon 0000:01:00.0: R_008010_GRBM_STATUS = 0xA0003030
Apr 28 16:24:18 mat-laptop kernel: [ 35.774808] radeon 0000:01:00.0: R_008014_GRBM_STATUS2 = 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [ 35.774811] radeon 0000:01:00.0: R_000E50_SRBM_STATUS = 0x200280C0
Apr 28 16:24:18 mat-laptop kernel: [ 35.774813] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [ 35.774815] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [ 35.774818] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [ 35.774820] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80100000
Apr 28 16:24:18 mat-laptop kernel: [ 35.780569] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Apr 28 16:24:18 mat-laptop kernel: [ 35.797540] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
Apr 28 16:24:18 mat-laptop kernel: [ 35.947561] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
Apr 28 16:24:18 mat-laptop kernel: [ 35.947598] radeon 0000:01:00.0: WB enabled
Apr 28 16:24:18 mat-laptop kernel: [ 35.947601] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880133b34c00
Apr 28 16:24:18 mat-laptop kernel: [ 35.947604] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xfff...

Apr 28 16:24:18 mat-laptop kernel: [   35.584061] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
Apr 28 16:24:18 mat-laptop kernel: [   35.584069] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001)
Apr 28 16:24:18 mat-laptop kernel: [   35.585105] radeon 0000:01:00.0: Saved 89 dwords of commands on ring 0.
Apr 28 16:24:18 mat-laptop kernel: [   35.585108] radeon 0000:01:00.0: GPU softreset: 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [   35.745021] radeon 0000:01:00.0:   R_008010_GRBM_STATUS      = 0xA0003030
Apr 28 16:24:18 mat-laptop kernel: [   35.745024] radeon 0000:01:00.0:   R_008014_GRBM_STATUS2     = 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [   35.745026] radeon 0000:01:00.0:   R_000E50_SRBM_STATUS      = 0x200200C0
Apr 28 16:24:18 mat-laptop kernel: [   35.745029] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [   35.745031] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [   35.745033] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000800
Apr 28 16:24:18 mat-laptop kernel: [   35.745036] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x800000C1
Apr 28 16:24:18 mat-laptop kernel: [   35.745038] radeon 0000:01:00.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
Apr 28 16:24:18 mat-laptop kernel: [   35.759919] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
Apr 28 16:24:18 mat-laptop kernel: [   35.774806] radeon 0000:01:00.0:   R_008010_GRBM_STATUS      = 0xA0003030
Apr 28 16:24:18 mat-laptop kernel: [   35.774808] radeon 0000:01:00.0:   R_008014_GRBM_STATUS2     = 0x00000003
Apr 28 16:24:18 mat-laptop kernel: [   35.774811] radeon 0000:01:00.0:   R_000E50_SRBM_STATUS      = 0x200280C0
Apr 28 16:24:18 mat-laptop kernel: [   35.774813] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [   35.774815] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [   35.774818] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
Apr 28 16:24:18 mat-laptop kernel: [   35.774820] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80100000
Apr 28 16:24:18 mat-laptop kernel: [   35.780569] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Apr 28 16:24:18 mat-laptop kernel: [   35.797540] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
Apr 28 16:24:18 mat-laptop kernel: [   35.947561] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
Apr 28 16:24:18 mat-laptop kernel: [   35.947598] radeon 0000:01:00.0: WB enabled
Apr 28 16:24:18 mat-laptop kernel: [   35.947601] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880133b34c00
Apr 28 16:24:18 mat-laptop kernel: [   35.947604] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff880133b34c0c
Apr 28 16:24:18 mat-laptop kernel: [   36.129762] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Apr 28 16:24:18 mat-laptop kernel: [   36.129765] [drm:r600_resume] *ERROR* r600 startup failed on resume

I suspect a regression introduced by hyperz support in mesa on ati...

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-01:

Could you add some info on your computer specifications?

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-01:

Same problem with xorg-edgers repository. After a ppa-purge xorg-edgers, it's now working... There must have been a very recent update that solved the problem. Thanks for your work !

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-01:

I tried the repository as well without a change of behaviour, but after a ppa-purge, my system still crashes. Could you verify, that you are definetly using the radeon-driver and not KMS or VESA now?

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-01:

#10

I attach here a glxinfo, it seems that I m using the radeon driver.
Hardware acceleration is working.

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-01:

#11

I do not see that from the glxinfo - did I overlook something? Could you verify via /var/log/Xorg.0.log?

From the specifications, you also seem to have the StudioXPS 1640?

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-01:

#12

Yes, I also have a Dell XPS 1640, if that still doesn't work for you, I don't understand why it is solved for me. Have you tried an apt-get upgrade ? Very strange...
Before this was solved this was my temporary solution : https://launchpad.net/~makson96/+archive/fglrx
I hope it will help you, but this problem stays with the opensource driver (eventhough I don't know why it's now working for me).

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-01:

#13

output.log Edit (4.3 KiB, text/plain)

From the Xorg.0.log, you do have the small non-RGBLED-Display, which is Not Full-HD? This might be the difference to mine.

Thanks for the tip with the downgrade-ppa, I'll test it later on. There still might be something left on your system from this ppa. Could you verify the appended list of package versions via 'dpkg -l|grep xserver-xorg'?

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-01:

#14

This bug occurs randomly (but it is very frequent). I have the problem again : GPU lockups during startup that result in a black screen after boot process. I think all people that have a xps 1640 with HD 3670 have the same problem...

Lars Kumbier (derlars) on 2013-05-01

Changed in xserver-xorg-video-ati (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-01:

#15

I can reproduce the problem every single time, so it might have something to do with the resolution or dependent things like the used graphic memory or the bandwidth... Do you have the amd64 version of ubuntu or the i386? If your system did boot up correctly, do you get the problem during the normal, daily usage or does it just occur during the boot process? Does the problem start right after the grub-menu or during the switch to the lightdm greeter?

For me, it's amd64 and the lockup always is during transition to the lightdm greeter. I've changed the status to confirmed due to two people being affected.

Bryce Harrington (bryce) on 2013-05-01

Changed in xserver-xorg-video-ati (Ubuntu):
status:	Confirmed → New

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-02:

#16

The workaround with the fglrx-legacy repository does work for me, thanks again for the tip.

Could you add some more info on your system (see previous post) and also report on the upstream bugtrack https://bugs.freedesktop.org/show_bug.cgi?id=64072, so that there's a bit more pressure on the development team of the open source radeon driver? Thanks!

bugbot (bugbot) on 2013-05-02

tags:

added: crash

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-09:

#17

This bug seems to be solved with linux 3.9 kernel ! Installing this package solved this bug :
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-05-09-saucy/linux-image-3.9.0-999-generic_3.9.0-999.201305090424_amd64.deb
Lars, does this solve the bug for you ?

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-11:

#18

Nice work, Mathieu!

It does fix the problem in single monitor mode. However, the 3d acceleration is deactivated and if I connect the 2nd monitor, unity crashes.

Even worse, after deinstallting the kernel und after reinstalling the fix from makson96, my desktop now does not have the unity bar and upper menubar anymore. I've tried updating initramfs, purging and reinstalling fglrx-legacy and unity-* - everything without effect. Compiz seems to work, as I do get window decorations and may size windows (started from a terminal via CTRL+ALT+T). Syslog and Xorg.0.log are unsuspicious.

Any ideas?

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-11:

#19

3d acceleration works for me using this have you tried ppa-purge to purge makson96 repository from your system ? Without having done that, xorg and other package stay in a downgraded version.
Try this :
sudo ppa-purge ppa:makson96/fglrx

Revision history for this message

Tournier Mathieu (mathieutournier) wrote on 2013-05-11:

#20

and don't forget to remove your xorg.conf

Revision history for this message

Lars Kumbier (derlars) wrote on 2013-05-11: Re: [Bug 1174042] Re: System crashes with open-source radeon driver

#21

I did purge the fglrx before installing the new kernel and do not have
an xorg.conf at all. I checked the correct use of the respective drivers
via the Xorg.0.log-output, so it's definetly the correct one. I'll check
the versions of some packages tomorrow. Thanks for the help!

Am 11.05.2013 19:34, schrieb Tournier Mathieu:
> and don't forget to remove your xorg.conf
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-08-15:

#22

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-ati (Ubuntu):
status:	New → Confirmed

Revision history for this message

krytek32 (nico-morris-beu6brc) wrote on 2013-08-15:

#23

Same problem for me:

I have ubuntu 13.04 and kde 4.11.
I removed my fglrx drivers, so I'm using open mesa drivers.
After reboot my maximum display resolution was 1280x1024, but my real maximum (that I correctly had with fglrx drivers) is 1920x1080.

I tried to do something from this wiki: https://wiki.ubuntu.com/X/Config/Resolution to section "Setting resolution changes in xorg.conf -- resolution lower than expected" but it didn't solve my problem, infact I tried to edit xorg.conf with the lines in the attached file but after reboot it says that my xorg.conf is not correctly configured and I had to remove xorg.conf and use the old one I had backed up before.

Besides I have "plasma-desktop" crash at startup (only without fglrx drivers, that is with open drivers).

I'll give you some information:

Crash log in "Developer Information" section of KDE Crash Assistant:
http://pastebin.com/raw.php?i=8stmVCky

xorg.conf:
http://pastebin.com/raw.php?i=D6MPUEZv

Xorg.0.log:
http://pastebin.com/raw.php?i=dWDVe03t

Revision history for this message

penalvch (penalvch) wrote on 2014-01-08:

#24

Lars Kumbier, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-video-ati REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs