Bug 111013

Summary: *ERROR* displayport link status failed/*ERROR* clock recovery failed
Product: DRI Reporter: Paul Menzel <pmenzel+bugs.freedesktop.org>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Linux 5.2-rc6 messages (dmesg) none

Description Paul Menzel 2019-06-27 09:41:51 UTC 
Created attachment 144652 [details]
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.
Comment 1 Paul Menzel 2019-06-27 09:45:09 UTC 
The system was in storage for a while, so no idea, when it started. It does not seem to happen with 4.19. Earliest Linux version I found in the logs showing these errors is 5.2-rc2.
Comment 2 Martin Peres 2019-11-19 09:31:51 UTC 
-- 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/836.

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.