* [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed
@ 2019-06-27 9:41 bugzilla-daemon
2019-06-27 9:45 ` bugzilla-daemon
2019-11-19 9:31 ` bugzilla-daemon
0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-06-27 9:41 UTC (permalink / raw)
To: dri-devel
[-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed
2019-06-27 9:41 [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed bugzilla-daemon
@ 2019-06-27 9:45 ` bugzilla-daemon
2019-11-19 9:31 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-06-27 9:45 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 400 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111013
--- Comment #1 from Paul Menzel <pmenzel+bugs.freedesktop.org@molgen.mpg.de> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1243 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed
2019-06-27 9:41 [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed bugzilla-daemon
2019-06-27 9:45 ` bugzilla-daemon
@ 2019-11-19 9:31 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-11-19 9:31 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111013
Martin Peres <martin.peres@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #2 from Martin Peres <martin.peres@free.fr> ---
-- 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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2428 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-11-19 9:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-27 9:41 [Bug 111013] *ERROR* displayport link status failed/*ERROR* clock recovery failed bugzilla-daemon
2019-06-27 9:45 ` bugzilla-daemon
2019-11-19 9:31 ` bugzilla-daemon
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.