From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56659] New: DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay
Date: Fri, 02 Nov 2012 06:19:11 +0000 [thread overview]
Message-ID: <bug-56659-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2455 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56659
Priority: medium
Bug ID: 56659
Assignee: dri-devel@lists.freedesktop.org
Summary: DRI_PRIME: triangle, rendering inside of which occurs
with a noticeable delay
Severity: normal
Classification: Unclassified
OS: All
Reporter: runetmember@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 69414
--> https://bugs.freedesktop.org/attachment.cgi?id=69414&action=edit
Example of artifact
Hello!
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.
Software:
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.
Hardware:
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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3937 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2012-11-02 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 6:19 bugzilla-daemon [this message]
2012-11-02 13:04 ` [Bug 56659] DRI_PRIME: triangle, rendering inside of which occurs with a noticeable delay bugzilla-daemon
2012-11-02 13:09 ` bugzilla-daemon
2012-11-27 18:11 ` bugzilla-daemon
2013-02-15 4:49 ` bugzilla-daemon
2013-05-04 20:08 ` bugzilla-daemon
2013-05-07 20:28 ` bugzilla-daemon
2013-05-07 22:16 ` bugzilla-daemon
2013-08-14 16:56 ` bugzilla-daemon
2015-09-08 18:19 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-56659-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).