Bug 56659 - DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay
Summary: DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2012-11-02 06:19 UTC by russianneuromancer
Modified: 2015-09-08 18:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Example of artifact (162.09 KB, image/jpeg)
2012-11-02 06:19 UTC, russianneuromancer
no flags Details

Description russianneuromancer 2012-11-02 06:19:11 UTC
Created attachment 69414 [details]
Example of artifact

Please look at attached screenshot - there is triangle where we still see part of old frame, that was displayed on screen few frames before. I doesn't sure about terminology, but from my point of view looks like rendering in this triangle is lag behind rest of the screen.
This issue happen for me only for applications launched with enabled offloading rendering (DRI_PRIME=1). It's reproducible not only in "Left 4 Dead 2" but also in other applications. Even in Chromium (if you launch it with "--ignore-gpu-blacklist" option that enabled hardware rendering on Mesa, and "DRI_PRIME=1" that enable offloading rendering) display same artifact (triangle) while scrolling pages. Also you may notice this artifact in glxgears, if you you run it in fullscreen mode.

Kubuntu 12.10 x86_64 updated from Xorg Edgers PPA.
Mesa: 9.1~git20121029.00e6819e
libdrm-radeon1: git20121025.bc494b31
xserver-xorg-video-radeon: git20120928.e8cb0b72
xserver-xorg-core: 1.13.0+git20120920.70e57668
Enabled or disabled V-Sync in KWin settings doesn't make the difference.
Enabled or disabled V-Sync in game settings doesn't make the difference.
Screenshot taken with stock Kubuntu kernel (3.5.0-17). With 3.7rc3 kernel issue still reproducible, but just a bit less noticeable.

Acer Aspire 7560G laptop,
AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO)
Discrete AMD Radeon HD 6650M (TURKS)

"xrandr --listproviders" output:
Providers: number : 2
Provider 0: id: 138 cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 1 name:radeon
Provider 1: id: 85 cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 1 name:radeon
Comment 1 Alex Deucher 2012-11-02 13:09:01 UTC
Please update to a newer xf86-video-ati snapshot.  You are missing some patches required for proper support with kwin.  Please reopen if you are still having issues with a newer snapshot.
Comment 2 russianneuromancer 2012-11-27 18:11:05 UTC
Unfortunately, still same issue with 7.0.99+git20121126.60cd6cea snapshot. Tested in Serious Sam 3.
Comment 3 russianneuromancer 2013-02-15 04:49:10 UTC
Still reproducible with radeon 7.0.0 and newer git snapshots.
Comment 4 russianneuromancer 2013-05-04 20:08:05 UTC
Still reproducible with radeon 7.1.0. Tested on native Left 4 Dead 2.
Comment 5 Jerome Glisse 2013-05-07 20:28:18 UTC
7.10 is old please try with at least 9.1
Comment 6 russianneuromancer 2013-05-07 22:16:46 UTC
Isn't 7.1.0 is latest version of the driver? http://www.x.org/wiki/radeon
If you talking about Mesa - sure, I already tried Mesa 9.1.1 and 9.2-git.
Comment 7 russianneuromancer 2013-08-14 16:56:13 UTC
Still issue with Linux 3.11rc5, radeon driver 7.1.99+git20130730.6a278369, Mesa 9.2.0~git20130729 and KDE 4.11rc2.
Comment 8 russianneuromancer 2015-09-08 18:19:08 UTC
Not reproducible anymore.

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.