After suspending to ram and resuming, many things appear blank, and dmesg has errors. In particular: icons for iconified windows, all non-core text (xterm with misc-fixed still works, but web browsers have nothing), images in web pages, the contents of windows (until they get redrawn). Restarting the X server fixes it. hardware: NVIDIA Corporation GF116M [GeForce GT 560M] (rev a1) versions: xorg: 1.15.0 nouveau: compiled for 1.15.0, module version = 1.0.10 libdrm: 2.4.52 mesa: 10.0.4 kernel: 3.14.19 I can try newer versions of particular things if it would be helpful, although I don't know which component would be relevant and I haven't seen any similar reports. I can also apply patches for more debugging info. The errors are a lot of lines like: [24060.452246] nouveau E[ PGRAPH][0000:01:00.0] TRAP ch 2 [0x005fba0000 X[2287]] [24060.452254] nouveau E[ PGRAPH][0000:01:00.0] SHADER 0xa004021e
Could you try booting with nouveau.config=PCE1=0 And seeing if that helps? This sounds like some resource copies aren't working properly (either on suspend or on resume) and some GF116's have been known to be silently missing their second copy engine (or we're not doing something to properly enable or we're not looking in the right place for the disable or ... who knows).
That seems to work, so I can just use that. Thanks! Let me know if you'd like me to test patches to handle this hardware automatically.
Well, first I'd like to get information... basically we need to figure out how to figure out that the second copy engine is busted. (Or, conversely, how to un-bust it.) Can you install envytools (https://github.com/envytools/envytools) and let's start with some easy stuff... as root, get the output of: nvapeek 22400 200
I get: 00022400: 00000000 00000000 00000000 00000002 00022410: 00000000 00000000 30000000 00000000 00022420: 00000000 00000000 00000800 00000000 00022430: 00000001 00000004 00000003 00000000 ...
After further investigation it appears that no GF116's actually contain a second "regular" copy engine, so it's been disabled completely. 3.18 should fix it and the patch is being backported to the stable trees.
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.