*ERROR* displayport link status failed/*ERROR* clock recovery failed

Submitted by Paul Menzel

Assigned to Default DRI bug account

Link to original bug (#111013)

Description

Created attachment 144652
Linux 5.2-rc6 messages (dmesg)

Using Linux 5.2-rc6 and the card below

$ lspci -nn -s 01:00.0
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (rev 81)

turning off and then back on the MST monitor Dell UP3214Q connected over DP, the errors below are shown. Sometimes it happens that the display won’t come back up.

[Wed Jun 26 15:50:41 2019] usb 1-10: USB disconnect, device number 4

→ turned monitor off

next morning turn it on:

[Thu Jun 27 10:39:39 2019] [drm:dce_v6_0_encoder_mode_set [amdgpu]] ERROR Couldn't read Speaker Allocation Data Block: -2
[Thu Jun 27 10:39:39 2019] [drm:dce_v6_0_encoder_mode_set [amdgpu]] ERROR Couldn't read SADs: -2
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] ERROR displayport link status failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] ERROR clock recovery failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] ERROR displayport link status failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] ERROR clock recovery failed

Please help me how to get to the bottom of why the clock recovery failed.

Attachment 144652, "Linux 5.2-rc6 messages (dmesg)":
linux-messages-5.2-rc6.txt