Bug 206021

Summary: AMDGPU/DC: freesync disabled on the monitor side after the monitor sleeps and resumes
Product: Drivers Reporter: Clément Guérin (libcg)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: RESOLVED MOVED    
Severity: normal CC: alexdeucher, bjo, harry.wentland, nicholas.kazlauskas
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.6 Subsystem:
Regression: No Bisected commit-id:
Attachments: Freesync ON
Freesync OFF
lock/resume with drm.debug=6
manually turning the monitor off and on with drm.debug=6

Description Clément Guérin 2019-12-30 20:39:15 UTC
Created attachment 286525 [details]
Freesync ON

linux 5.4.6
xorg-server 1.20.6
xf86-video-amdgpu 19.1.0
mesa 19.3.1
gnome-shell 3.34.2
R9 Fury
Samsung C27HG70 with 1023.0 firmware

Steps to reproduce:
- Hit Super+L to lock screen
- Wait for the monitor to turn off (blinking status LED)
- Wake up screen by hitting any key

Before going to sleep, the monitor will show that Freesync is active in the OSD (see freesync_on.jpg attachment). After sleep, Freesync will be disabled in the OSD (see freesync_off.jpg). However the driver still thinks Freesync is active: in games, the screen will turn blank when the framerate goes below 144Hz. It's possible to recover by replugging the displayport cable or by manually powering the monitor off and back on.
Comment 1 Clément Guérin 2019-12-30 20:39:34 UTC
Created attachment 286527 [details]
Freesync OFF
Comment 2 Clément Guérin 2019-12-31 06:14:12 UTC
Created attachment 286533 [details]
lock/resume with drm.debug=6
Comment 3 Clément Guérin 2019-12-31 06:17:15 UTC
Created attachment 286535 [details]
manually turning the monitor off and on with drm.debug=6
Comment 4 Clément Guérin 2020-02-02 18:44:59 UTC
Still an issue as of linux 5.5.1.

Interestingly the Freesync state recovers if I reboot my computer instead of turning my monitor off and on. This suggests the monitor itself is not at fault and there might be some missing initialization on screen wakeup.
Comment 5 Clément Guérin 2020-02-15 21:55:06 UTC
Hitting that bug on linux 5.6-rc1
Comment 6 Clément Guérin 2020-03-25 22:29:37 UTC
Is anyone looking at this? I can still reproduce the bug 100%.
Comment 7 Clément Guérin 2020-04-13 22:04:50 UTC
No improvement on 5.7-rc1
Comment 8 Clément Guérin 2020-04-21 23:26:28 UTC
Moving to https://gitlab.freedesktop.org/drm/amd/-/issues/1112