I've noticed that there sometimes was tearing (vsync off) when framerate was below VRR range minimum (which is 40 - 144Hz in my case), e.g. in some game's videos that run with 30fps and probably also if framerate rapidly drops below VRR range. I found a way to reliably reproduce the issue during actual game rendering: Start vkquake and load a level. Game's default limiter is set to 200. Open game's console via tilde key (English keyboard layout, button below ESC) and set fps to 35 (should be below any display's VRR range minimum) by typing "host_maxfps 35". -> FreeSync LFC should be broken now and show tearing if vsync isn't turned on. When changing again to a value that's inside the VRR range, e.g. 100, VRR works perfectly again. When switching back to 35, it's once again broken. The Windows driver doesn't seem to show this issue. linux 5.2.9 (also tested drm-next branch) xf86-video-amdgpu-git e6fce59a071220967fcd4e2c9e4a262c72870761 RX 570 radv of mesa-git ACO branch fc0fdb637b4a028816f5a59b14eda07612e1bc9b
I think there is a realistic chance that this issue has been tackled by this commit: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.5-wip&id=109b3e3e13507ad0908ff00bc7eb759ed41b88be However, I don't own an LFC capable display anymore and can't test. Though I think it might be a candidate for backporting to 5.4?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/894.
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.