From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed Date: Thu, 27 Jun 2019 09:41:51 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1285135161==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CAC626E84E for ; Thu, 27 Jun 2019 09:41:51 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1285135161== Content-Type: multipart/alternative; boundary="15616285110.f4628936C.23982" Content-Transfer-Encoding: 7bit --15616285110.f4628936C.23982 Date: Thu, 27 Jun 2019 09:41:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D111013 Bug ID: 111013 Summary: *ERROR* displayport link status failed/*ERROR* clock recovery failed Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: pmenzel+bugs.freedesktop.org@molgen.mpg.de Created attachment 144652 --> https://bugs.freedesktop.org/attachment.cgi?id=3D144652&action=3Dedit 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=E2=80= =99t come back up. [Wed Jun 26 15:50:41 2019] usb 1-10: USB disconnect, device number 4 =E2=86=92 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]] *ER= ROR* displayport link status failed [Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER= ROR* clock recovery failed [Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER= ROR* displayport link status failed [Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER= ROR* clock recovery failed Please help me how to get to the bottom of why the clock recovery failed. --=20 You are receiving this mail because: You are the assignee for the bug.= --15616285110.f4628936C.23982 Date: Thu, 27 Jun 2019 09:41:51 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 111013
Summary *ERROR* displayport link status failed/*ERROR* clock recovery= failed
Product DRI
Version XOrg git
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter pmenzel+bugs.freedesktop.org@molgen.mpg.de 

Created attachmen=
t 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=E2=80=
=99t come
back up.

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

=E2=86=92 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]] *ER=
ROR*
displayport link status failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER=
ROR*
clock recovery failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER=
ROR*
displayport link status failed
[Thu Jun 27 10:39:40 2019] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ER=
ROR*
clock recovery failed

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

You are receiving this mail because:
  • You are the assignee for the bug.
= --15616285110.f4628936C.23982-- --===============1285135161== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1285135161==--