From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105530] Stuttering on Raven Ridge when TearFree is on
Date: Wed, 21 Mar 2018 05:26:12 +0000 [thread overview]
Message-ID: <bug-105530-502-rcJzFvDSlj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105530-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1150 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105530
--- Comment #5 from txtsd <thexerothermicsclerodermoid@gmail.com> ---
(In reply to Michel Dänzer from comment #4)
> (In reply to txtsd from comment #0)
> > The stuttering is caused by enabling TearFree via xrandr.
> > When on `auto`, there is no stuttering, but when enabled by setting it to
> > `on`, there is intense stuttering noticeable when dragging windows around,
> > but it's also very noticeable when just moving the mouse around on the
> > desktop with no windows open.
>
> Since HW cursor updates are always supposed to work without delay, and there
> is no sign of an issue in the attached userspace information, this seems
> like a kernel (DC?) issue.
>
> In the amd-gfx mailing list thread, you said that this started on
> 2018-03-07. Is that just when you enabled TearFree for the first time, or
> did this actually not happen with older kernels?
Yep. That was the first time I altered the TearFree property, and that's when
it first appeared. I hadn't noticed it prior to that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-21 5:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-105530-502@http.bugs.freedesktop.org/>
2018-03-16 9:41 ` [Bug 105530] Stuttering on Raven Ridge when TearFree is on bugzilla-daemon
2018-03-21 5:26 ` bugzilla-daemon [this message]
2018-03-21 11:58 ` bugzilla-daemon
2018-03-24 12:18 ` bugzilla-daemon
2018-04-03 9:31 ` bugzilla-daemon
2018-04-27 11:23 ` bugzilla-daemon
2018-09-16 0:52 ` bugzilla-daemon
2018-09-17 3:47 ` bugzilla-daemon
2018-09-17 4:16 ` bugzilla-daemon
2018-09-17 7:51 ` bugzilla-daemon
2018-09-17 8:11 ` bugzilla-daemon
2018-09-17 10:38 ` bugzilla-daemon
2018-11-23 22:22 ` bugzilla-daemon
2018-11-24 9:37 ` bugzilla-daemon
2018-11-26 2:01 ` bugzilla-daemon
2019-01-13 15:34 ` bugzilla-daemon
2019-05-19 18:42 ` bugzilla-daemon
2019-11-19 8:32 ` 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-105530-502-rcJzFvDSlj@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