Created attachment 77476 [details] crashes with compiz and red eclipse When running anything 3D, the GPU has a very high chance of locking up within anywhere from 2 minutes to an hour. When running a 3D application while using Compiz, that time is decreased even further and can happen in just seconds of launching the other 3D application. It makes using this GPU almost impossible for anything besides 2D applications. This is an EVGA GeForce GTX 660, 2 GB model. Attached are two dmesg logs I saved during/after the GPU had crashed.
Created attachment 77480 [details] compiz crash - reuploaded Re-uploading the crashes. They were in a tar.gz file but apparently bugzilla doesn't like that very much.
Created attachment 77481 [details] red eclipse crash - reuploaded
Created attachment 77483 [details] another crash...
Created attachment 77484 [details] ...another...
Changing version to git as I have just compiled the latest mesa + drivers and this is still an issue.
Created attachment 77550 [details] minetest crash Uploading another crash, hopefully these will be helpful to somebody...
Created attachment 77551 [details] firefox running on compiz
Created attachment 78027 [details] GPU lockup with latest git Updated to latest git, still an issue...
Created attachment 78028 [details] corruption screenshot
Created attachment 78030 [details] one more...
Created attachment 78439 [details] minetest on openbox Another crash occurred just now. Though I doubt anybody's going to even look at this bug at this point, I thought I'd upload this anyway...
Please try a 3.11-rc kernel. There have been various kepler updates since 3.8. Also, I only looked at your latest log, but I did see a suspend/resume sequence in there. I assume you can get it to crash without a suspend/resume in there as well?
Hi Ilia, Yes, I can get it to crash without doing a suspend/resume. The latest kernel I tried is 3.10.7, but I will try a 3.11 kernel when I'm able to. For now, I'm just living off of Openbox and applications that only use 2D (which actually isn't as bad as I thought it'd be).
(In reply to comment #13) > Hi Ilia, > Yes, I can get it to crash without doing a suspend/resume. The latest kernel > I tried is 3.10.7, but I will try a 3.11 kernel when I'm able to. For now, > I'm just living off of Openbox and applications that only use 2D (which > actually isn't as bad as I thought it'd be). Linux 3.11 contains many fixes concerning context switching which should fix your 3D issues.
Created attachment 84990 [details] neverball+compiz I installed 3.11-rc7 and while I'm still having issues with Compiz, everything else seems to be working fine, which leads me to believe that Compiz is probably what's at fault now. Tried with Xonotic, Minetest, Neverball and am going to try to leave Red Eclipse running for a while just to see if there are any crashes. If it doesn't crash, I'll go ahead and mark this up to Compiz being at fault now. I'll go ahead and upload the dmesg output of Compiz+Neverball crashing if you want to view it and tell me if it's still a nouveau issue or if it is a Compiz issue at this point. Thanks for your help!
I do note lots of errors in your dmesg, make sure you're using the latest mesa as well (9.2 is probably good enough, don't know if too much stuff has happened on 9.3-devel yet).
Compiled the latest Mesa (9.2) from git today, still having lockup issues.
I have the same exact card, and am having the same exact issue. I was planning on doing tests with 3x 1080p monitors. I can go about 10 minutes with everything working perfectly. Then i get a GPU Lockup. Currently im running Arch Linux with cinnamon 2.0. So i should be using the latest releases of everything. I will try and get log next time I get a crash
Is this the same as https://bugs.freedesktop.org/show_bug.cgi?id=72180 (which has a lot more info on the issue)? Does using blob graph fw help?
*** This bug has been marked as a duplicate of bug 72180 ***
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.