From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111506] [amdgpu] VRR/Freesync below the range (LFC) flickering (5700 XT) Date: Wed, 28 Aug 2019 08:26:53 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0177898310==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 5DA2F898F3 for ; Wed, 28 Aug 2019 08:26:53 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0177898310== Content-Type: multipart/alternative; boundary="15669808130.37fc07.14271" Content-Transfer-Encoding: 7bit --15669808130.37fc07.14271 Date: Wed, 28 Aug 2019 08:26:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D111506 Bug ID: 111506 Summary: [amdgpu] VRR/Freesync below the range (LFC) flickering (5700 XT) Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: not set Priority: not set Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: asheldon55@gmail.com I'm getting heavy flickering when dropping below the minimum refresh rate (default of 40-92, but I also tested 35-92) with Freesync enabled. It seems to be LFC related as the higher the minimum, the earlier the flickering kicks in (so it's not a case of the monitor not being able to ha= ndle it at the low end). I can workaround the problem by changing block of code in freesync.c: if (in_out_vrr->max_refresh_in_uhz < (2 * in_out_vrr->min_refresh_in_uhz)) in_out_vrr->btr.btr_enabled =3D false; with: if (in_out_vrr->max_refresh_in_uhz < (3 * in_out_vrr->min_refresh_in_uhz)) in_out_vrr->btr.btr_enabled =3D false; effectively forcing LFC to only kick in at ~30fps or lower.=20 It's possibly a regression as I don't remember the issue occurring with Veg= a or Polaris and 5.2 kernel. It's also possible that it's the monitor itself at fault, and maybe LFC wasn't kicking in properly in older kernels/hardware, effectively hiding the problem. I will try to get around to testing with Ve= ga and an older kernel in the future. System: MSI 5700 XT amd-staging-drm-next Mesa git --=20 You are receiving this mail because: You are the assignee for the bug.= --15669808130.37fc07.14271 Date: Wed, 28 Aug 2019 08:26:53 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 111506
Summary [amdgpu] VRR/Freesync below the range (LFC) flickering (5700 = XT)
Product DRI
Version DRI git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity not set
Priority not set
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter asheldon55@gmail.com

I'm getting heavy flickering when dropping below the minimum r=
efresh rate
(default of 40-92, but I also tested 35-92) with Freesync enabled.

It seems to be LFC related as the higher the minimum, the earlier the
flickering kicks in (so it's not a case of the monitor not being able to ha=
ndle
it at the low end).

I can workaround the problem by changing block of code in freesync.c:

if (in_out_vrr->max_refresh_in_uhz <
            (2 * in_out_vrr->min_refresh_in_uhz))
                in_out_vrr->btr.btr_enabled =3D false;

with:

if (in_out_vrr->max_refresh_in_uhz <
            (3 * in_out_vrr->min_refresh_in_uhz))
                in_out_vrr->btr.btr_enabled =3D false;

effectively forcing LFC to only kick in at ~30fps or lower.=20

It's possibly a regression as I don't remember the issue occurring with Veg=
a or
Polaris and 5.2 kernel. It's also possible that it's the monitor itself at
fault, and maybe LFC wasn't kicking in properly in older kernels/hardware,
effectively hiding the problem. I will try to get around to testing with Ve=
ga
and an older kernel in the future.


System:
MSI 5700 XT
amd-staging-drm-next
Mesa git


You are receiving this mail because:
  • You are the assignee for the bug.
= --15669808130.37fc07.14271-- --===============0177898310== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0177898310==--