Bug 76076 - Catalan driconf translation causes bad performance and graphical corruption with vsync in kwin
Summary: Catalan driconf translation causes bad performance and graphical corruption w...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-12 12:40 UTC by Christoph Haag
Modified: 2014-03-24 22:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Christoph Haag 2014-03-12 12:40:26 UTC 
Okay, get ready for an esoteric bug report. I can't even begin to formulate any thoughts on why any of this happens.

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

Also I have this in the same machine, but I hope it doesn't matter:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff)


Problems I see with kwin vsync with "full screen repaints" or whatever it is called in english:
* At the top of the screen over the whole width some white artifacts are flickering but then mostly vanishing after a while.
* In title bars there's sometimes a white bar over the top maybe 1/4 of the title bar, sometimes a bit flickering.
* corruption around the mouse pointer in some areas on the screen, during taking screenshots it flickers to the normal mouse pointer, here's a bad picture of it: http://i.imgur.com/0Rztnru.png
* Bad performance, i.e. laggy, when moving windows around and using gui elements like dropdownboxes. Usable, but noticeably laggy. gtkperf is ~5 seconds with vsync vs. ~3 seconds without vsync. Without the problematic commit it is ~3 seconds for both cases.

When using "automatic" vsync in kwin it is much better with the corruption and artifacts, but the performance when moving windows is initially still bad, but gets better after maybe half a second.

When using no vsync in kwin I think there are no issues at all.

I have bisected it to d5e5367e8992c2e5322d35fba8d86c33a0db6825 which adds catalan translations to driconf, and only i965_dri.so needs to be replaced to make the issue appear/disappear. I couldn't really believe it, but yet here I am.

This is compiled with -march=native on ivy bridge with these configure options http://pastebin.com/raw.php?i=1kUkiFCX

84529a5ddb214961d0a743c68a4b8e13fb7ab34b: http://w3studi.informatik.uni-stuttgart.de/~haagch/i965_dri.so.good

d5e5367e8992c2e5322d35fba8d86c33a0db6825: http://w3studi.informatik.uni-stuttgart.de/~haagch/i965_dri.so.bad

Since d5e5367e8992c2e5322d35fba8d86c33a0db6825 I have seen this right up until latest git master. Reverting this commit makes the issues go away.

I'm using de_DE.UTF8, if that makes a difference. gcc 4.8.2 on archlinux.
Comment 1 Christoph Haag 2014-03-24 22:32:05 UTC 
Well, then.

I am sorry I can't give you closure to this.

I can only say that at the moment I can *not* reproduce this with recent mesa git  (0d99aef).

With the "bad" i965_dri.so I posted here I *can* reproduce it.


If I have some time to kill in the future I will investigate in probably this order:

* Compile and test the "bad" revision again to see if some change outside of mesa fixed it
* compile with different optimization levels. Maybe there is a fringe issue somewhere there
* if not: git bisect again to find the first good revision after the "bad" ones.

I'll mark it as fixed for now until I find anything that could at least begin to offern an explanation for this.


What I forgot to mention the first time: This is mostly happening with two monitors with 1920x1080@60 Hz, the one on the right is my laptop LVDS and primary, the one on the left is connected by DVI ("HDMI1") and better, but not completely gone with only one screen.

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.