Created attachment 96381 [details] dmesg When I run the game bastion there is screen corruption, and after some time the computer locks up. The menu renders OK-ish (with only some flickering corruption). When ingame, the screen flickers between (mostly) uncorrupted and corrupted at random intervals. After some time the computer crashes. Before the crash there is a lot of output in dmesg by nouveau. I am running archlinux. Versions: xorg 1.15.0 mesa 10.1.0 xf86-video-nouveau 1.0.10 nouveau-dri 10.1.0 linux 3.13.7
Can you check with 3.14-rc8? Alternatively try booting with nouveau.config=PCRYPT=0. (Although I'm not seeing the MMIO write error that I would expect to see if you had that particular issue, but it's easy enough to try.) The final crash is due to running out of vram, which I guess is handled less-than-perfectly by mesa. I'd prefer to focus on the initial corruption.
Created attachment 96385 [details] dmesg with 3.14-rc8
Created attachment 96386 [details] dmesg with 3.14-rc8 and nouveau.config=PCRYPT=0
There is no change in the behaviour, with 3.14-rc8 kernel with or without nouveau.config=PCRYPT=0.
Created attachment 96387 [details] Picture of corruption 1 Sorry, couldn't get a real screenshot, so only a photo
Created attachment 96388 [details] Picture of corruption 2
If you capture an apitrace of the game, do you still see the corruption when replaying the trace?
With apitrace I couldn't get past the menu without the game becoming unresponsive, but there is already some corruption. The trace is too big to attach, I have uploaded it at http://blankertz.org/~matthias/Bastion.bin.x86.3.trace
As of linux 3.14.1 (mesa version unchanged) the rendering errors in the menu are gone, the rendering errors in game are still present but the system no longer crashes. Attaching new dmesg. Versions: xorg 1.15.1 mesa 10.1.0 xf86-video-nouveau 1.0.10 nouveau-dri 10.1.0 linux 3.14.1
Created attachment 97415 [details] dmesg with 3.14.1
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1061.
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.