Bug 110138 - Adaptive Sync, VRR, FreeSync out of range
Summary: Adaptive Sync, VRR, FreeSync out of range
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-16 02:30 UTC by grmat
Modified: 2019-04-04 17:25 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
raw edid (256 bytes, application/octet-stream)
2019-03-16 02:30 UTC, grmat
no flags Details
parsed edid (2.27 KB, text/plain)
2019-03-16 02:31 UTC, grmat
no flags Details
0001-drm-amd-display-Only-allow-VRR-when-vrefresh-is-with.patch (1.72 KB, patch)
2019-03-18 13:04 UTC, Nicholas Kazlauskas
no flags Details | Splinter Review

Description grmat 2019-03-16 02:30:51 UTC
Created attachment 143688 [details]
raw edid

Hi,

my monitor has a FreeSync range from 35 to 90 Hz. The maximum supported refresh rate is 144, which I use by default.

When switching mode to a refresh rate >90 (120 or 144), the monitor's HUD says that FreeSync is now disabled. On Windows, this is the case.

However, VRR is still being enabled with 144 Hz on Linux 5.0, mesa 19 and xf86-video-amdgpu 19. It results in heavy artifacts, the timing is broken so that even the monitor HUD is broken.

I've attached the monitor's EDID.

Regards
Comment 1 grmat 2019-03-16 02:31:27 UTC
Created attachment 143689 [details]
parsed edid
Comment 2 Michel Dänzer 2019-03-18 10:09:51 UTC
Please attach the corresponding Xorg log file and output of dmesg.
Comment 3 Nicholas Kazlauskas 2019-03-18 13:04:32 UTC
Created attachment 143724 [details] [review]
0001-drm-amd-display-Only-allow-VRR-when-vrefresh-is-with.patch

I think this patch should fix your issue. We previously blocked enabling it if vrefresh < min supported range, but we didn't cover vrefresh > max supported range.
Comment 4 grmat 2019-04-04 17:25:52 UTC
> I think this patch should fix your issue

Indeed it does, thanks! :)

I've seen it is already in for 5.1. Don't you think it should be backported for 5.0 as well? I'm not sure if the issue could damage the display but for what I can tell, it's a serious bug and surely looks disturbing to users.


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.