(Forwarding this from original bug reporter at http://launchpad.net/bugs/692755 )
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: 18.104.22.168 (2.6.37 git checkout from 20101220 also tested)
Does a newer kernel (2.6.36 or 2.6.37) help?
Created attachment 41317 [details]
kernel log showing the problem
(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
Created attachment 41318 [details] [review]
Does this kernel patch help?
Created attachment 41322 [details]
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
A video of the corruption can be seen here:
Hi, I can work around this problem by booting with "nomodeset".
Is this still an issue with a newer kernel?
Downstream report invalid.