Corrupt graphics on resume from S4

Bug #692755 reported by Steve Magoun
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xserver-xorg-driver-ati
Invalid
Medium
xserver-xorg-video-ati (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xorg

I'm unable to resume from S4 on a Lenovo ThinkPad SL510 w/ ATI Mobility Radeon 4570 (1002:9553). Upon entering S4, the graphics become corrupt - it looks a bit like an X11 stipple or that checkerboard that used to be the X background (though it's not just B&W, there is some R/G/B in the pattern. The pattern is not as random as static; it appears tiled, as if we're displaying tiles populated with corrupt video memory.

On resume from hibernate, the BIOS logo is not corrupt and the (not-corrupted) plymouth logo flashes for an instant. There are several seconds of a flashing white cursor at the top left of the screen too. Once X comes back I see the stipple pattern/corruption again. Both the X and console sessions are corrupted. There is a separate corrupt tile surrounding the mouse cursor (the cursor itself is not visible). Moving the mouse cursor results in the mouse-tile moving around. The machine is otherwise functional - I can (blindly) login to a console on a VT and execute commands.

Syslog from the failed resume session shows errors from drm:radeon, starting with:

Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671568] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671570] [drm:rv770_resume] *ERROR* r600 startup failed on resume

If I disable the radeon driver by adding, e.g., the made-up 'radeon.nofailboat=1' kernel parameter, the machine enters and resumes from S4 normally, with no corruption upon either entering or resuming from S4.

I've reproduced in both the stock 10.10 kernel and the daily natty kernel (2.6.37-999-generic #201012200905).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
Uname: Linux 2.6.37-999-generic i686
Architecture: i386
Date: Mon Dec 20 16:16:40 2010
InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 20101216-14:50
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.37-999-generic

Revision history for this message
In , Robert Hooker (sarvatt) wrote :

(Forwarding this from original bug reporter at http://launchpad.net/bugs/692755 )

Description:

Graphics get corrupted before the machine enters S4. I don't have a camera handy, but it's a grey pattern that looks a bit like an old-fashioned X11 stipple (though it's not just B&W, there is some R/G/B in the pattern. The pattern is not as random as static; it appears tiled, as if we're displaying tiles populated with corrupt video memory.

On resume from hibernate, the BIOS logo is not corrupt and the (not-corrupted) plymouth logo flashes for an instant. There are several seconds of a flashing white cursor at the top left of the screen too. Once X comes back I see the stipple pattern/corruption again. Both the X and console sessions are corrupted. There is a separate corrupt tile surrounding the mouse cursor (the cursor itself is not visible). Moving the mouse cursor results in the mouse-tile moving around. The machine is otherwise functional - I can (blindly) login to a console on a VT and execute commands.

Syslog from the failed resume session shows errors from drm:radeon, starting with:

Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671568] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)
Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671570] [drm:rv770_resume] *ERROR* r600 startup failed on resume

Then hundreds of the following, with different values of IB

Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1029.211800] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11).
Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1029.211847] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1029.212731] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1029.212773] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

If I disable the radeon driver by adding, e.g., the made-up 'radeon.nofailboat=1' kernel parameter, the machine enters and resumes from S4 normally, with no corruption upon either entering or resuming from S4.

This is on Ubuntu 10.10 with these components:

Kernel: 2.6.35.8 (2.6.37 git checkout from 20101220 also tested)
libdrm: 2.4.21
xf86-video-ati: 6.13.1
mesa: 7.9-git20100924

Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

Does a newer kernel (2.6.36 or 2.6.37) help?

Revision history for this message
In , Robert Hooker (sarvatt) wrote :

Created attachment 41317
kernel log showing the problem

Revision history for this message
In , Robert Hooker (sarvatt) wrote :

(In reply to comment #1)
> Does a newer kernel (2.6.36 or 2.6.37) help?

He tried a git checkout from today with no luck, up to commit 55ec86f848a5f872fd43f5d7206464a0af419110

Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

Created attachment 41318
possible fix

Does this kernel patch help?

Revision history for this message
In , Robert Hooker (sarvatt) wrote :

Created attachment 41322
kernel log with patch

It didn't help unfortunately

[ 45.741351] radeon 0000:01:00.0: GPU softreset
[ 45.741354] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0x00003028
[ 45.741357] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000002
[ 45.741359] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0
[ 45.741373] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE

Revision history for this message
Steve Magoun (smagoun) wrote :
Chris Van Hoof (vanhoof)
tags: added: hwe-blocker
Revision history for this message
Robert Hooker (sarvatt) wrote :
affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Changed in xserver-xorg-video-ati (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Robert Hooker (sarvatt)
description: updated
Revision history for this message
Chris Van Hoof (vanhoof) wrote :
Revision history for this message
Steve Magoun (smagoun) wrote :

kern.log from a test w/ patch from the fdo bug. The patch didn't cause any change in behavior. Look for the 's4test' kernel in the log.

Revision history for this message
In , Robert Hooker (sarvatt) wrote :

A video of the corruption can be seen here:

http://sarvatt.com/downloads/sl510-bug-691324.mov

bugbot (bugbot)
tags: added: corruption
tags: added: resume
Changed in xserver-xorg-driver-ati:
status: Unknown → Confirmed
Changed in xserver-xorg-driver-ati:
importance: Unknown → Medium
Revision history for this message
RickDole (rdole1) wrote :

I found this to be the case on both my netbook and desktop. On the desktop (a nividea card) I can at least fall back to a properly displayed vc and reboot. On the netbook, I am forced to do the same, only the vc is also corrupted, so login is blind.

Revision history for this message
aaron (microsoftenator) wrote :

This bug is still present in Oneiric. I have the exact same GPU (Radeon 4570) in a Dell Studio 15 and get the exact same results from attempting to hibernate and resume.

Revision history for this message
madbiologist (me-again) wrote :

Firstly, sorry for the vagueness of the comment I am about to make.

While looking through kernel and freedesktop radeon bugs a while ago I came accross a screenshot that matches the description in this bug. I can't remember the exact hardware the reporter was using, but the problem had been fixed with a patch. Unfortunately I can't remember which kernel version had the fix, but it was before the currently-under-development 3.6, so I suggest trying Ubuntu 12.10 "Qantal Quetzal" beta 2 which is based on the upstream 3.5 kernel.

Please let us know whether the problem occurs or not on Ubuntu 12.10 "Qantal Quetzal" beta 2.

Changed in xserver-xorg-video-ati (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
In , Jeroen--klomp (jeroen--klomp) wrote :

Hi, I can work around this problem by booting with "nomodeset".

Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

Is this still an issue with a newer kernel?

Revision history for this message
RickDole (rdole1) wrote :

On a clean install of beta 2, I'm not sure how to enter S4 properly, as it seems to be disabled. I installed the hibernate scripts and ran them from xterm. The machine comes back up exactly from where it left off, without even the screen lock.

Rajiv Shah (rajivshah3)
Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → New
status: New → Confirmed
assignee: nobody → Rajiv (compukid)
assignee: Rajiv (compukid) → nobody
description: updated
Revision history for this message
Greg (cebif) wrote :

I am seeing the same bug in precise, kernel 3.2.0-44-generic. I have a AMD HD7850 graphics card, on a desktop machine. After rersume from hibernate the screen is corrupted, similar to previous discriptions.
I press CTRL + ALT + F1, to fall back to a console then login. There is no corrution in the console. I then use command: sudo top.
I kill xorg with top. Immediately xorg restarts and a normal graphical uncorruted login screen appears. From there I login to unity and everything works fine but this bug needs to be fixed because there is no way to resume to a previous desktop state.
My graphics driver is: amd-catalyst-13.4-linux-x86.x86_64 proprietary download and install from the AMD site.
xorg version: 1:7.6+12ubuntu2
xserver-xorg-core: version 2:1.11.4-0ubuntu10.13
xserver-xorg-video-s3: version 1:0.6.3-4build2
xserver-xorg-input-all: version 1:7.6+12ubuntu2
xserver-xorg-video-all: version 1:7.6+12ubuntu2
libx11-data: version 2:1.4.99.1-0ubuntu2.1
python-xkit: version 0.4.2.3build1

Revision history for this message
Greg (cebif) wrote :

Here is two xsession files. The old one that finished updating after logging in this morning with resume from hibernate and the new one after that.

Revision history for this message
penalvch (penalvch) wrote :

Steve Magoun, 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

Changed in xserver-xorg-video-ati (Ubuntu):
importance: High → Low
status: Confirmed → Incomplete
Revision history for this message
Steve Magoun (smagoun) wrote :

@Christopher - I no longer have access to the hardware in the original report, sorry.

Revision history for this message
penalvch (penalvch) wrote :

Steve Magoun, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/692755/comments/13 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
In , penalvch (penalvch) wrote :

Downstream report invalid.

Changed in xserver-xorg-driver-ati:
status: Confirmed → Invalid
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.