dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202445] New: amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering
Date: Tue, 29 Jan 2019 04:53:31 +0000	[thread overview]
Message-ID: <bug-202445-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=202445

            Bug ID: 202445
           Summary: amdgpu/dc: framerate dropping below adaptive sync
                    range causes screen flickering
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.0rc4
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: libcg@protonmail.com
        Regression: No

linux 5.0rc4
mesa 4aa64940c
xf86-video-amdgpu a1b479c

hardware:
- R9 Fury
- Samsung C27HG70 (1020.0 firmware, Freesync Ultimate Engine)

I'm running the Unigine Valley benchmark extremely smoothly as long as the
framerate stays in between 48-144fps. When it drops below that, I'm observing
heavy stuttering and flickering in the darker parts of the image. The
flickering also affects the loading screen when frames are rendered very
infrequently.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-01-29  4:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  4:53 bugzilla-daemon [this message]
2019-01-29 14:48 ` [Bug 202445] amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering bugzilla-daemon
2019-01-29 15:46 ` bugzilla-daemon
2019-01-29 15:47 ` bugzilla-daemon
2019-01-30 14:02 ` bugzilla-daemon
2019-01-30 16:50 ` bugzilla-daemon
2019-01-30 16:53 ` bugzilla-daemon
2019-01-30 17:04 ` bugzilla-daemon
2019-01-31  5:36 ` bugzilla-daemon
2019-01-31  6:17 ` bugzilla-daemon
2019-02-02 22:39 ` bugzilla-daemon
2019-02-03 23:28 ` bugzilla-daemon
2019-02-03 23:51 ` bugzilla-daemon
2019-02-04  4:59 ` bugzilla-daemon
2019-02-04 15:44 ` bugzilla-daemon
2019-02-04 16:41 ` bugzilla-daemon
2019-02-07  8:00 ` bugzilla-daemon
2019-02-07 14:24 ` bugzilla-daemon
2019-02-25 19:13 ` bugzilla-daemon
2019-02-28  4:57 ` bugzilla-daemon
2019-03-01 16:43 ` bugzilla-daemon
2019-03-01 16:45 ` bugzilla-daemon
2019-03-01 16:54 ` bugzilla-daemon
2019-03-11 15:45 ` bugzilla-daemon
2019-03-15 15:57 ` bugzilla-daemon
2019-03-16  8:30 ` bugzilla-daemon
2019-03-18 13:07 ` bugzilla-daemon
2019-03-18 15:25 ` bugzilla-daemon
2019-03-18 17:44 ` bugzilla-daemon
2019-03-28  3:45 ` bugzilla-daemon
2019-04-28  0:57 ` bugzilla-daemon
2019-04-29 13:31 ` bugzilla-daemon
2019-06-03 10:56 ` bugzilla-daemon
2019-09-16  2:33 ` bugzilla-daemon
2019-09-16 13:22 ` bugzilla-daemon
2019-09-16 14:58 ` bugzilla-daemon
2019-09-16 15:02 ` bugzilla-daemon
2020-02-15 23:20 ` bugzilla-daemon
2020-04-07 15:07 ` bugzilla-daemon
2020-04-07 15:10 ` 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-202445-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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).