Suspending/resuming to ram works fine, but thawing from hibernate causes a blank screen and an unresponsive keyboard. SSH works fine though. Disabling kernel mode setting works but then the display resolution is really lmited and only parts of the desktop is visible. Some kind of timeout? root@bergarn:~# uname -a Linux bergarn 3.1.0-1-amd64 #1 SMP Tue Jan 10 05:01:58 UTC 2012 x86_64 GNU/Linux root@bergarn:~# dmesg | grep drm <snip> [ 375.581395] [drm] nouveau 0000:01:00.0: Disabling fbcon acceleration... [ 375.581399] [drm] nouveau 0000:01:00.0: Unpinning framebuffer(s)... [ 375.581482] [drm] nouveau 0000:01:00.0: Evicting buffers... [ 376.577978] [drm] nouveau 0000:01:00.0: Idling channels... [ 376.578088] [drm] nouveau 0000:01:00.0: Suspending GPU objects... [ 376.871211] [drm] nouveau 0000:01:00.0: And we're gone! [ 378.558456] [drm] nouveau 0000:01:00.0: We're back, enabling device... [ 378.558471] [drm] nouveau 0000:01:00.0: POSTing device... [ 378.558474] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0x7D74 [ 378.608964] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0x8497 [ 378.641548] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0x9AD6 [ 378.641799] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0x9AE0 [ 378.642700] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0x9CB5 [ 378.642701] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0x9D1A [ 380.628904] [drm] nouveau 0000:01:00.0: 0x9D1A: Condition still not met after 2000ms, skipping following opcodes [ 380.630216] [drm] nouveau 0000:01:00.0: Restoring GPU objects... [ 380.640617] [drm] nouveau 0000:01:00.0: Reinitialising engines... [ 380.640909] [drm] nouveau 0000:01:00.0: Restoring mode... [ 382.640908] [drm] nouveau 0000:01:00.0: timeout: CURSOR_CTRL2_STATUS_ACTIVE(0) [ 382.640961] [drm] nouveau 0000:01:00.0: CURSOR_CTRL2(0) = 0x00000000 </snip> Machine is a Clevo P170HM with Intel Q2760M and Geforce GTX 560M.
You might want to take this up with your distribution. This issue should have been fixed in upstream code a while back.
(In reply to comment #1) > You might want to take this up with your distribution. This issue should have > been fixed in upstream code a while back. Thanks for your comment. This might be fixed by the 3.2 kernel which will be available soon in Debian wheezy. If that doesn't solve it I'll revisit this. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659110
Unfortunately an upgrade to the 3.2 kernel didn't fix the issue. Do you have commit IDs for the fix?
Rikard tried v3.3-rc3 with the same result. http://bugs.debian.org/659110#75
Please re-test with the latest kernel (3.11-rc7). If problems persist, please supply the information requested at http://nouveau.freedesktop.org/wiki/Bugs/.
No response to re-test request for over a month. Closing as invalid.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.