Bug 95413 - Oversaturation + Artifacts on screen refresh with Redwood GPU
Summary: Oversaturation + Artifacts on screen refresh with Redwood GPU
Status: RESOLVED NOTABUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 11.2
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-15 21:52 UTC by Sawyer Bergeron
Modified: 2016-05-19 16:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
1st file of those requested (80.32 KB, text/x-log)
2016-05-16 23:17 UTC, Sawyer Bergeron
Details
2nd file requested (23.49 KB, text/x-log)
2016-05-16 23:18 UTC, Sawyer Bergeron
Details
3rd file requested (78.74 KB, text/plain)
2016-05-16 23:18 UTC, Sawyer Bergeron
Details
4th file requested (78.40 KB, text/plain)
2016-05-16 23:18 UTC, Sawyer Bergeron
Details

Description Sawyer Bergeron 2016-05-15 21:52:55 UTC
In any compositor (XRender still affected, but to lesser degree) the screen first appears somewhat oversaturated/of too high contrast, but on each subsequent screen redraw the entire screen becomes less and less possible to decipher until it becomes 2 bit black and white for every part of the screen except for the areas that were most recently refreshed (while other parts of the screen were redrawn, even if not refreshed.)

This bug occurs in Gnome 3, Plasma (4 and 5), and Unity, though it has no effect on non X-sessions, nor does it appear to affect login screens (sddm, gdm, or lightdm). Sessions composited using XRender are oversaturated/have too high a contrast and are oddly colored, but do not exhibit increasing saturation/contrast issues on redraw. OpenGL 2/3 are worst using GXL, though OpenGL 3 with EGL is sometimes somewhat better (though far worse than XRender.)

For a graphics card, I use a FirePro v4800 (based on Redwood XT, I believe) 

If a screenshot would help, please let me know so I can post one
Comment 1 Alex Deucher 2016-05-16 13:28:39 UTC
Please attach your xorg log, glxinfo output, and dmesg output.  Also what versions of mesa, ddx, xserver, and kernel are you running?
Comment 2 Sawyer Bergeron 2016-05-16 23:17:45 UTC
Created attachment 123798 [details]
1st file of those requested

Uname -r returns "4.4.0-22-generic"
X -version returns "1.18.3"
I have no idea how to check ddx, but if necessary I can with instruction (probably)

Here are the files you requested
Comment 3 Sawyer Bergeron 2016-05-16 23:18:06 UTC
Created attachment 123799 [details]
2nd file requested
Comment 4 Sawyer Bergeron 2016-05-16 23:18:24 UTC
Created attachment 123800 [details]
3rd file requested
Comment 5 Sawyer Bergeron 2016-05-16 23:18:40 UTC
Created attachment 123801 [details]
4th file requested
Comment 6 Sawyer Bergeron 2016-05-19 16:16:21 UTC
It would appear that there was a small issue regarding the card--there was some cat fur blocking the fan from spinning at full speed, and something was causing the motor to not compensate for that resistance. The card ended up getting fairly hot during operation, and it appears after cleaning the card that it is operating normally now. Sorry for the inconvenience this oversight on my part caused.


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.