linux-image-3.2.0-31-generic-pae radeon regression

[Roman Shipovskij]

after upgrading to linux-image-3.2.0-31-generic-pae system boot stop on message (dmesg):
...
[ 24.640329] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec
[ 24.640339] GPU lockup (waiting for 0x00000003 last fence id 0x00000001)
[ 24.641547] radeon 0000:00:01.0: GPU softreset
[ 24.641551] radeon 0000:00:01.0: GRBM_STATUS=0xF5704828
[ 24.641556] radeon 0000:00:01.0: GRBM_STATUS_SE0=0xFE000001
[ 24.641560] radeon 0000:00:01.0: GRBM_STATUS_SE1=0x00000007
[ 24.641564] radeon 0000:00:01.0: SRBM_STATUS=0x20020940
[ 24.791683] radeon 0000:00:01.0: Wait for MC idle timedout !
[ 24.791687] radeon 0000:00:01.0: GRBM_SOFT_RESET=0x00007F6B
[ 24.791792] radeon 0000:00:01.0: GRBM_STATUS=0x00003828
[ 24.791796] radeon 0000:00:01.0: GRBM_STATUS_SE0=0x00000007
[ 24.791800] radeon 0000:00:01.0: GRBM_STATUS_SE1=0x00000007
[ 24.791804] radeon 0000:00:01.0: SRBM_STATUS=0x20020940
[ 24.792806] radeon 0000:00:01.0: GPU reset succeed
[ 24.946601] radeon 0000:00:01.0: Wait for MC idle timedout !
[ 25.100666] radeon 0000:00:01.0: Wait for MC idle timedout !
[ 25.104499] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 25.104618] radeon 0000:00:01.0: WB enabled
[ 25.277944] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
[ 25.277951] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume

as result black screen and system accessible only over ssh

with linux-image-3.2.0-30-generic-pae boot is success

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-generic-pae 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
Uname: Linux 3.2.0-31-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu13
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfeb40000 irq 16'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,104384b0,00100001'
   Controls : 17
   Simple ctrls : 9
Date: Fri Sep 28 22:27:38 2012
HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
MachineType: ASUSTeK Computer Inc. ET2011A
ProcEnviron:
 TERM=xterm
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic-pae root=UUID=4f7459a9-c139-4407-b0b2-9ed2111ff8ea ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-generic-pae N/A
 linux-backports-modules-3.2.0-31-generic-pae N/A
 linux-firmware 1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2011
dmi.bios.vendor: ASUSTeK Computer Inc.
dmi.bios.version: 0405
dmi.board.name: ET2011A
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 0405
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 13
dmi.chassis.vendor: Compal
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnASUSTeKComputerInc.:bvr0405:bd08/19/2011:svnASUSTeKComputerInc.:pnET2011A:pvr0405:rvnASUSTeKComputerInc.:rnET2011A:rvr0405:cvnCompal:ct13:cvrChassisVersion:
dmi.product.name: ET2011A
dmi.product.version: 0405
dmi.sys.vendor: ASUSTeK Computer Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/

[Roman Shipovskij (roman-shipovskij)]

I install latest v3.6 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/:
linux-image-3.6.0-030600rc7-generic_3.6.0-030600rc7.201209232235_i386.deb
linux-image-extra-3.6.0-030600rc7-generic_3.6.0-030600rc7.201209232235_i386.deb

everything looked good, but after 3rd reboot I got a black screen as described in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029159

and a lot of errors in dmesg:
radeon 0000:00:01.0: couldn't schedule ib
[drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !

after that i reboot system more than 30 times but can't reproduce that again and all works fine

[Roman Shipovskij (roman-shipovskij)]

after some time i reboot system again and get black screen again 2 times with errors in dmesg:
radeon 0000:00:01.0: couldn't schedule ib
[drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !

in latest v3.6 kernel exist another bug, kernel before linux-image-3.2.0-31-generic-pae doesn't have this problem

[Simon Déziel (sdeziel)]

I can confirm this also happens on latest 64 bit Precise kernel. The latest Quantal kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/) is not affected so far (4 reboots OK already).

[Luis Henriques (henrix)]

It looks like one of the commits in the radeon driver that is included in the 3.2.0-31.50 Ubuntu kernel has been recently reverted upstreams. This commit (985f61f7ee647ad570c05eab0b74915da2ac8e19 "drm/radeon: rework pll selection (v3)") seems to cause some regressions.

This may not be related with this bug report, but I'm building a test kernel with this commit reverted so that you can test. I'll post the link here once the build is complet.

[Simon Déziel (sdeziel)]

Hi Luis, according to the changelog, 3.2.0-31.50 does not have the commit in question while 3.2.0-32.51 (-proposed) does. Both kernels are showing the problematic behaviour here. Thanks for looking into this, much appreciated.

[Luis Henriques (henrix)]

Hi Simon, you're absolutely right: thanks for paying attention to that. Now, I took another look at the changelog and here's the list of "suspicious" commits in that version:

be05980 drm/radeon: do not reenable crtc after moving vram start address
899d1d5 drm/radeon: fix bank tiling parameters on cayman
8b4d42b drm/radeon: fix bank tiling parameters on evergreen

What I've done was to build a new test kernel with these 3 commits reverted and uploaded it here:

http://people.canonical.com/~henrix/lp1058303/v1/

(there's a 32 bits and a 64 bits version).

Could someone having this issue give it a try (picking the correct version)? If reverting these commits solves the problem, we will need to find out exactly which one(s) is the responsible for the issue.

[Simon Déziel (sdeziel)]

Hi Luis, so far so good, 18 reboots without problem using the 64bit build, thanks!

I'm available for more testing if needed to isolate the faulty commit(s) out of the 3 reverted ones.

[Roman Shipovskij (roman-shipovskij)]

Hi all, after more than 30 reboots with 32 bit kernel no problems detected.

I'm also available for more testing if needed, thanks!

[Luis Henriques (henrix)]

Great, thank you for testing these kernels. So, I've uploaded a new test kernel, this time reverting only the 2 first patches, leaving commit 8b4d42b drm/radeon: fix bank tiling parameters on evergreen. Here's the link:

http://people.canonical.com/~henrix/lp1058303/v2/

[Simon Déziel (sdeziel)]

Luis, 30 successful reboots with the "v2" kernel

[Roman Shipovskij (roman-shipovskij)]

Hi, 20 successful reboots using 32 bit "v2" kernel

[Luis Henriques (henrix)]

Great, thank you for testing these kernels. So, I've uploaded a new test kernel, this time reverting only the 2 first patches, leaving commit 8b4d42b drm/radeon: fix bank tiling parameters on evergreen. Here's the link:

http://people.canonical.com/~henrix/lp1058303/v2/

[Simon Déziel (sdeziel)]

Luis, comment #14 is a copy of #11. Did you mean to post a "v3" instead? I couldn't find new kernel in http://people.canonical.com/~henrix/lp1058303/ though.

[Luis Henriques (henrix)]

Ups, not sure what happen with the comments duplication...

Anyway, I've uploaded another test kernel:

http://people.canonical.com/~henrix/lp1058303/v3/

This kernel contains:
899d1d5 drm/radeon: fix bank tiling parameters on cayman
8b4d42b drm/radeon: fix bank tiling parameters on evergreen

reverting only:
be05980 drm/radeon: do not reenable crtc after moving vram start address

[Roman Shipovskij (roman-shipovskij)]

Hi, 20 successful reboots using 32 bit "v3" kernel

[Simon Déziel (sdeziel)]

35 successful reboots with the 64 bit "v3" kernel.

[Luis Henriques (henrix)]

Great, so from all these tests, we could say that the faulty commit is:

  be05980 drm/radeon: do not reenable crtc after moving vram start address

(it could also be a combination of these 3 commits...)

So, I've built a (final??) test kernel that contains only:

  be05980 drm/radeon: do not reenable crtc after moving vram start address

and reverts:
  899d1d5 drm/radeon: fix bank tiling parameters on cayman
  8b4d42b drm/radeon: fix bank tiling parameters on evergreen

All going well, this kernel should *fail* :-)

Here's the link:

http://people.canonical.com/~henrix/lp1058303/v4/

[Roman Shipovskij (roman-shipovskij)]

5 of 12 reboots failed with error:

[drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
[drm:evergreen_resume] *ERROR* evergreen startup failed on resume

[Simon Déziel (sdeziel)]

The 12th reboot using the 64 bit version of "v4" failed with this error:

[ 407.891033] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15).
[ 407.891048] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !

[Luis Henriques (henrix)]

I've reporter this upstream. It looks like commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 ("drm/radeon: properly handle
mc_stop/mc_resume on evergreen+ (v2)") should fix it without the need to revert the offending commit. Thus, I've built a test kernel that I would like you to try. Unfortunately, the commit had a few dependencies and I had to cherry-pick a few other commits. Here's the list of commits included in the test kernel:

3ae19b750bdc09ce233e1504348320141593ffda drm/radeon/kms: add wait_for_vblank asic callback
89e5181f3f79fbe46dbf811f9bc470f524704450 drm/radeon/kms: add a radeon asic callback for mc idle
8848f759c0de139bada271aa446f48637c98ca1a drm/radeon/kms: add trinity (TN) chip family
4a15903db02026728d0cf2755c6fabae16b8db6a drm/radeon/dce4+: don't use radeon_crtc for vblank callback
62444b7462a2b98bc78d68736c03a7c4e66ba7e2 drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2)

Here's the link to the kernel:

http://people.canonical.com/~henrix/lp1058303/v5/

[Roman Shipovskij (roman-shipovskij)]

30 successful reboots using 32 bit "v5" kernel

[Simon Déziel (sdeziel)]

34 successful reboots with 64 bit "v5" kernel

[Luis Henriques (henrix)]

Great! You guys are really fast! :-)
Thank you for all the testing. I'll follow this up upstreams and get it fixed soon.

[Simon Déziel (sdeziel)]

On 12-10-05 02:27 PM, Luis Henriques wrote:
> Great! You guys are really fast! :-)
> Thank you for all the testing. I'll follow this up upstreams and get it fixed soon.

Thanks goes to you for helping us! I appreciate your work!

[Luis Henriques (henrix)]

I've followed this issue upstreams and a patch has been proposed to solve the issue. Basically, it is the same as the one in comment #22 (commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2), but without all the other commits listed. This patch is a backport containing already all the dependencies, and will probably be the one accepted upstreams.

As usual, I've uploaded a new test kernel containing this solution. Could you please give it a quick test and confirm this also fixes the issue? Here's the link:

http://people.canonical.com/~henrix/lp1058303/v6/

Thank you.

[Roman Shipovskij (roman-shipovskij)]

20 successful reboots using 32 bit "v6" kernel

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "Ben Hutchings' backport" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Simon Déziel (sdeziel)]

31 successful reboots using 64 bit "v6" kernel

[Roman Shipovskij (roman-shipovskij)]

new kernel with regression again in precise-updates (3.2.0-32)?

[Cosimo (cosimo)]

I've tried 3.2.0-32 (#51) AMD64 but it freezes may be more frequently than 3.2.0-31, I still must use 3.2.0-30.
In which kernel version will the patch be available?

[Simon Déziel (sdeziel)]

On 12-10-14 10:16 PM, Cosimo wrote:
> I've tried 3.2.0-32 (#51) AMD64 but it freezes may be more frequently than 3.2.0-31, I still must use 3.2.0-30.
> In which kernel version will the patch be available?

@Cosimo, just to make you have that exact bug, do you have an ATI/AMD
graphic card that gives a black screen once in a while on boot while the
box still answers to ping/SSH? Or are you see an actual freeze (no
SSH/ping)?

[Cosimo (cosimo)]

@Simon, i'm usibng a Acer Apire One 722 (about video card, lspci says: "00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6290]").

syslog says:
Oct 14 21:19:16 pangoo kernel: [ 37.914704] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
Oct 14 21:19:16 pangoo kernel: [ 37.914715] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume

I'm not sure if it replies to ping or ssh, but after the blank screen I can hear the login screen sound, so I guess the PC is still working. I can experience the blank screen more or less once every two reboot. It started after kernel upgrade to 3.2.0-31.

Yesterday I upgraded to -32 but it didn't solve. Now I've setup the 3.2.0-30 as default kernel on grub.

[Simon Déziel (sdeziel)]

On 12-10-15 03:40 AM, Cosimo wrote:
> @Simon, i'm usibng a Acer Apire One 722 (about video card, lspci says:
> "00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
> Wrestler [Radeon HD 6290]").
>
> syslog says:
> Oct 14 21:19:16 pangoo kernel: [ 37.914704] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
> Oct 14 21:19:16 pangoo kernel: [ 37.914715] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume
>
> I'm not sure if it replies to ping or ssh, but after the blank screen I
> can hear the login screen sound, so I guess the PC is still working. I
> can experience the blank screen more or less once every two reboot. It
> started after kernel upgrade to 3.2.0-31.
>
> Yesterday I upgraded to -32 but it didn't solve. Now I've setup the
> 3.2.0-30 as default kernel on grub.

That looks like the same bug indeed. You can give a try to the kernel
built by Luis:

http://people.canonical.com/~henrix/lp1058303/v6/

It should fix your problem until an official Ubuntu kernel integrates
the patches.

[Matt Behrens (zigg)]

I believe I have this issue with my AO722 on quantal, though my symptoms are a little different as I have a cryptsetup root, so I never get to the passphrase prompt. I do typically get a black screen on first boot, but can ctrl-alt-del, and boot proceeds normally the second time through.

My question is this: the test kernels henrix posted are 3.2 series. quantal's on 3.5. Can I use these safely? Or should I expect quantal to have this fix integrated?

[Simon Déziel (sdeziel)]

@Matt, Quantal should eventually get the fix too but for testing you can give a try to the kernel posted by henrix.

[Matt Behrens (zigg)]

Thanks. I did try it and it didn't do anything for my symptoms, unfortunately; I'm probably barking up the wrong tree.

The comments in this bug did prompt me, however, to try blindly typing my passphrase in to unlock the drive, which worked, surprisingly. And with that, once X starts, the display works...

[Simon Déziel (sdeziel)]

On 12-10-19 10:33 AM, Matt Behrens wrote:
> The comments in this bug did prompt me, however, to try blindly typing
> my passphrase in to unlock the drive, which worked, surprisingly. And
> with that, once X starts, the display works...

Indeed this doesn't look like the same bug. Could you try to confirm you
don't have the same log errors in syslog when it happens? Could this be
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/939283 ? If not,
that would worth reporting a new bug.

[Luis Henriques (henrix)]

This bug is awaiting verification that the kernel for Precise in -proposed solves the problem (3.2.0-33.52). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-precise' to 'verification-done-precise'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Roman Shipovskij (roman-shipovskij)]

50 successful reboots using 32 bit 3.2.0-33.52 pae kernel from precise-proposed

[Daniel Rocher (daniel-rocher)]

It's work for me (kernel amd64 3.2.0-33.52).

Thank you !

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.2.0-33.52

---------------
linux (3.2.0-33.52) precise-proposed; urgency=low

  [Luis Henriques]

  * Release Tracking Bug
    - LP: #1067666

  [ Andy Whitcroft ]

  * [Config] add fs/udf to linux-image to support DVD/CD formats in virtual
    instances
    - LP: #1066921

  [ James M Leddy ]

  * SAUCE: input: fix weird issue of synaptics psmouse sync lost after
    resume
    - LP: #717970

  [ Paolo Pisati ]

  * [SRU] [Config] enable TIDSPBRIDGE for omap arm[el|hf] flavours
    - LP: #1058022

  [ Sarveshwar Bandi ]

  * SAUCE: bridge: Pull ip header into skb->data before looking into ip
    header.
    - LP: #1065150

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: rework pll selection (v3)"
    - LP: #1065047
  * sched: Fix migration thread runtime bogosity
    - LP: #1057593
  * Bluetooth: Add support for Sony Vaio T-Series
    - LP: #1054307
  * drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2)
    - LP: #1058303
  * Bluetooth: Use USB_VENDOR_AND_INTERFACE() for Broadcom devices
    - LP: #1058303
  * Bluetooth: Add USB_VENDOR_AND_INTERFACE_INFO() for Broadcom/Foxconn
    - LP: #1030233, #1058303
  * target: Fix ->data_length re-assignment bug with SCSI overflow
    - LP: #1065047
  * ASoC: samsung dma - Don't indicate support for pause/resume.
    - LP: #1065047
  * fs/proc: fix potential unregister_sysctl_table hang
    - LP: #1065047
  * mm/ia64: fix a memory block size bug
    - LP: #1065047
  * nbd: clear waiting_queue on shutdown
    - LP: #1065047
  * drivers/rtc/rtc-twl.c: ensure all interrupts are disabled during probe
    - LP: #1065047
  * mm/page_alloc: fix the page address of higher page's buddy calculation
    - LP: #1065047
  * memory hotplug: fix section info double registration bug
    - LP: #1065047
  * cciss: fix handling of protocol error
    - LP: #1065047
  * vfs: dcache: use DCACHE_DENTRY_KILLED instead of DCACHE_DISCONNECTED in
    d_kill()
    - LP: #1065047
  * workqueue: reimplement work_on_cpu() using system_wq
    - LP: #1065047
  * cpufreq/powernow-k8: workqueue user shouldn't migrate the kworker to
    another CPU
    - LP: #1065047
  * sched: Fix ancient race in do_exit()
    - LP: #1065047
  * hpwdt: Fix kdump issue in hpwdt
    - LP: #1065047
  * rtlwifi: rtl8192ce: Log message that B_CUT device may not work
    - LP: #1065047
  * brcmfmac: fix big endian bug in i-scan.
    - LP: #1065047
  * brcmfmac: Fix big endian host configuration data.
    - LP: #1065047
  * dmaengine: at_hdmac: fix comment in atc_prep_slave_sg()
    - LP: #1065047
  * dmaengine: at_hdmac: check that each sg data length is non-null
    - LP: #1065047
  * ARM: 7532/1: decompressor: reset SCTLR.TRE for VMSA ARMv7 cores
    - LP: #1065047
  * drm/i915: Reduce a pin-leak BUG into a WARN
    - LP: #1065047
  * bnx2i: Fixed NULL ptr deference for 1G bnx2 Linux iSCSI offload
    - LP: #1065047
  * mpt2sas: Fix for issue - Unable to boot from the drive connected to HBA
    - LP: #1065047
  * hwmon: (ads7871) Add 'name' sysfs attribute
    - LP: #1065047
  * DMA: PL330: Check the pointer returned by kzalloc
    - LP: #1065047
  * hpsa: fix handling of protocol error
    -...

[Adam Conrad (adconrad)]

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

[Herton R. Krzesinski (herton)]

Development task (raring) is fix released, "drm/radeon: properly handle
mc_stop/mc_resume on evergreen+ (v2)" is already included in raring.

[Julian Wiedmann (jwiedmann)]

The patch noted in #45 has landed in quantal-updates with 3.5.0-22.33, so presumably it's fixed there too.