From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed
Date: Thu, 27 Jun 2019 09:41:51 +0000 [thread overview]
Message-ID: <bug-111013-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1998 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111013
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=144652&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3445 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-27 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 9:41 bugzilla-daemon [this message]
2019-06-27 9:45 ` [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed bugzilla-daemon
2019-11-19 9:31 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111013-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.