Bug 32933 - Screen corruption with drm-nouveau-next
Summary: Screen corruption with drm-nouveau-next
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-09 02:37 UTC by Lucas Stach
Modified: 2011-01-23 08:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Example of screen corruption (385.71 KB, image/png)
2011-01-09 02:37 UTC, Lucas Stach 		no flags Details
View All

Description Lucas Stach 2011-01-09 02:37:30 UTC 
Created attachment 41786 [details]
Example of screen corruption

If I use drm-nouveau-next instead of master I get massive screen corruption after some minutes working with X. The corruption never appears directly after starting X, it takes several minutes to show up.

Restarting X hides the problem for a few minutes before the corruption reappears.

DDX and libdrm are from git as of 08-Jan-2011.

I tried to use "EXAOptimizeMigration" "off" in xorg.conf, but this has no effect.
Comment 1 Lucas Stach 2011-01-09 03:09:41 UTC 
Forget to mention:
Xorg-server is 7.4 from Fedora 14 stock
graphics adapter is nvA0
Comment 2 Ben Skeggs 2011-01-09 03:35:57 UTC 
Can you post dmesg please. Also, any chance of finding which commit is responsible. Thanks :)
Comment 3 Lucas Stach 2011-01-09 09:23:59 UTC 
Logs do not contain anything interesting.

But I bisected the issue today. It seems the problematic commit is 5f6fdca570b13a8a2c9cab9ab6edfc17487049cf
Comment 4 Ben Skeggs 2011-01-15 01:52:27 UTC 
Can you try drm-nouveau-staging, there's a fix to nouveau_mm.c that appears to fix the issues I seen on my NVA0.
Comment 5 Lucas Stach 2011-01-23 08:40:15 UTC 
Yes, code from drm-nouveau-staging seems to fix it. I used this for several hours now and haven't seen any corruption.

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.