Bug 76605

Summary: [NV86] Screen corruption and crashes in bastion on NVS-140M
Product: Mesa Reporter: Matthias Blankertz <matthias>
Component: Drivers/DRI/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: 10.1   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: dmesg
dmesg with 3.14-rc8
dmesg with 3.14-rc8 and nouveau.config=PCRYPT=0
Picture of corruption 1
Picture of corruption 2
dmesg with 3.14.1

Description Matthias Blankertz 2014-03-25 20:40:13 UTC
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
Comment 1 Ilia Mirkin 2014-03-25 20:51:12 UTC
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.
Comment 2 Matthias Blankertz 2014-03-25 22:51:12 UTC
Created attachment 96385 [details]
dmesg with 3.14-rc8
Comment 3 Matthias Blankertz 2014-03-25 22:51:56 UTC
Created attachment 96386 [details]
dmesg with 3.14-rc8 and nouveau.config=PCRYPT=0
Comment 4 Matthias Blankertz 2014-03-25 22:52:58 UTC
There is no change in the behaviour, with 3.14-rc8 kernel with or without nouveau.config=PCRYPT=0.
Comment 5 Matthias Blankertz 2014-03-25 22:56:21 UTC
Created attachment 96387 [details]
Picture of corruption 1

Sorry, couldn't get a real screenshot, so only a photo
Comment 6 Matthias Blankertz 2014-03-25 22:57:51 UTC
Created attachment 96388 [details]
Picture of corruption 2
Comment 7 Ilia Mirkin 2014-03-25 23:13:08 UTC
If you capture an apitrace of the game, do you still see the corruption when replaying the trace?
Comment 8 Matthias Blankertz 2014-03-25 23:56:30 UTC
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
Comment 9 Matthias Blankertz 2014-04-15 14:10:22 UTC
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
Comment 10 Matthias Blankertz 2014-04-15 14:10:53 UTC
Created attachment 97415 [details]
dmesg with 3.14.1
Comment 11 GitLab Migration User 2019-09-18 20:39:22 UTC
-- 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.