[Bug 32535] New: Graphics corruption after resume from hibernate on Thinkpad SL510 (RV710 0x1002:0x9553)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=32535

           Summary: Graphics corruption after resume from hibernate on
                    Thinkpad SL510 (RV710 0x1002:0x9553)
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: sarvatt at gmail.com
         QAContact: xorg-team at lists.x.org


(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

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.