Description of problem: I come back to my desktop and the lockscreen is up (monitors not asleep) but frozen and unresponsive. No mouse pointer, no response to keyboard <enter>, <ctrl-alt-F3>, etc. Machine is accessible over ssh and otherwise fine. Version-Release number of selected component (if applicable): Up-to-date Fedora Workstation 25 (beta) on Lenovo P710 with Radeon RX480, three displays. How reproducible: Happened twice today. I don't know how to trigger it. Steps to Reproduce: 1. boot system 2. log in 3. wait? :/ Actual results: Lock screen unresponsive. Expected results: Screens stay asleep until input is detected, then lockscreen transitions to login prompt. Additional info: journalctl says from the time of the freeze: Nov 03 10:03:24 nanger kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed Nov 03 10:03:24 nanger kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed Nov 03 10:03:24 nanger kernel: [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to get vblank before flip
This is Fedora 25, so it's using wayland instead of X; not sure xorg-x11-drv-amdgpu is the correct component.
Happened again Tuesday on 4.8.6-300.fc25.x86_64.
Happened again today on 4.8.6-300.fc25.x86_64.
Also happens with 4.8.7-300.fc25.x86_64.
And with 4.8.8-300.fc25.x86_64. I wonder if this is related to bug 1392119. I haven't been able to reproduce it if I turn off all but one display before the lock screen engages.
Happened today with 4.8.12-300.fc25.x86_64.
This still occurs occasionally, but not as frequently as it did earlier.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
I haven't seen this recently. Closing.