Title says it all :p
* Screen is frozen but uncorrupted.
* Mouse cursor moves with the touchpad, but the external mouse doesn't move it.
* ctrl-alt-f1 doesn't change VTs
* magic sysrq keys work, although sysrq-v causes "BUG: scheduling while atomic: swapper/0/0x10010000"
* I can ssh into the machine, and it seems to be otherwise working properly
Suspending from a vt works fine, although after resuming I can't switch back to X (hangs in the same way).
Linux cwillu-acer 2.6.30-999-generic #1243674012 SMP Sat May 30 09:44:52 UTC 2009 i686 GNU/Linux
Output of intel_gpu_dump from vt1 before suspending: http://launchpadlibrarian.net/27425610/pre-suspend
Output of intel_gpu_dump from vt1 immediately after resuming: http://launchpadlibrarian.net/27425564/post-suspend
Photo of image corruption on the rare otherwise-successful resume: http://cwillu.com/images/resume-corruption.jpg
Occasionally the resume still succeeds (I'd say less than 10% of the time). There's a variable amount of corruption of text at that point (every instance of specific letters) that goes away when bouncing to another vt and back.
Running intel_gpu_top after a failed resume shows:
ring idle: 0% ring space: 272/126976 (0%)
task percent busy
Bypass FIFO: 100%
Color calculator: 100%
Pixel shader: 100%
Other potentially relevant logs are listed at https://bugs.launchpad.net/xorg-server/+bug/382884/comments/1
[Increasing priority since this is a freeze with the official stack KMS/UXA/GEM.]
Incidentally, hibernation works fine (7 cycles so far). I'll attach before/after intel_gpu_dump's in a moment.
Let me revise that: occasionally when a suspend works, it will continue to work dozens of times in a row. I think that's what happened this last time with the hibernation, when I tried it again with instrumentation, I just got the broken behavior again.
I'll try get a before/after dump the next time it works for a long string of attempts again, in the mean time, I'm attaching the before/after dumps from the hibernate.
maybe dup with bug#22010
I filed bug #22285 which looks very similar.
*** This bug has been marked as a duplicate of bug 20520 ***