Created attachment 106428 [details] dmesg of cs:go lockup im getting a regression with 3.17 gpu lockups instantly i launch wine/cs:go and at random times with just normal X usage. i bisected the kernel twice and ended up on same commit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f331a15f84a94dce6f12cf0b7012174b4a6bf804 this is on a 780ti. attaching dmesg of wine/csgo lockup on 3.17-rc5 and X lockup with the bisected kernel at that commit.
Created attachment 106429 [details] dmesg of x lockup
however reverting e887377338f and 67cfbfdfec9fa so f331a15f84a cleanly reverts i still get the X lockups
checking out a2d58c33a doesnt make X nor cs:go lockup however it artifacts badly, and spams dmesg with this https://gist.github.com/anonymous/f53c93768a9ba1ca0ee0 . tried setting drivers/gpu/drm/nouveau/core/engine/graph/ctxgk110b.c bundle_token_limit to 0x7c0 instead of 0x600 but no dice. screenshot of it artifacting http://i.imgur.com/HLb8I6t.png and the artifacts isnt contained to cs:go they go out on X aswell as you can see on dropbox systray icon and garbles some text everywhere.
What's the last commit where everything works properly? We should start from there. You mention you still get X lockups even after reverting f331a?
(In reply to comment #4) > What's the last commit where everything works properly? We should start > from there. > > You mention you still get X lockups even after reverting f331a? yea that is the weird thing reverting those 3 commits it still lockups but going cleanly to its parent it only artifacts, after some bisecting the first bad commit with artifacts is 694c6caf92615828dbfd3fc30e937c8f54d2ac93 , so the first commit where everything works is ac9738bb3e5374495908ad236285f69cfd405f8e
seems to be working now with kernel 3.18.2
Created attachment 112412 [details] [review] patch for lockups. thanks to xexaxo from #d3d9 on freenode.
fixed in linux 4.0 , https://github.com/torvalds/linux/commit/404ba3f79089a01c1ebacccafa08a5db4a4cd2af
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.