dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100745] amdgpu fails to wake up DisplayPort DELL monitors with 'clock recovery failed'
Date: Fri, 06 Oct 2017 00:36:30 +0000	[thread overview]
Message-ID: <bug-100745-502-VNWpYiVA8T@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100745-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1292 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100745

Eddie Ringle <eddie@ringle.io> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eddie@ringle.io

--- Comment #6 from Eddie Ringle <eddie@ringle.io> ---
Wanted to add that I'm seeing this issue now under a similar setup. I've seen
it in the past, but the last few kernel releases have been pretty smooth. Once
I upgraded to GNOME 3.26, however, both 4.13 and now 4.14-rc3 are displaying
this issue.

I'm on Arch (using Wayland primarily), with a Fury X and three Dell P2415Q
monitors, also connected via DisplayPort. I have MST disabled on all three,
since (even Dell has documented) this model has issues hitting 4K@60Hz with it
enabled.

Same "displayport link status failed" and "clock recovery failed" messages
appear for me, also three times in a row. This more often than not leads to
gnome-shell crashing. I see it most often after I've put my computer to sleep
when I try to wake it up. Other times when putting it to sleep, one monitor
will stay powered and show a backlit blank screen.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2724 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-10-06  0:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  4:01 [Bug 100745] amdgpu fails to wake up DisplayPort DELL monitors with 'clock recovery failed' bugzilla-daemon
2017-04-21  4:12 ` bugzilla-daemon
2017-04-21  4:45 ` bugzilla-daemon
2017-04-21  6:36 ` bugzilla-daemon
2017-04-21 13:20 ` bugzilla-daemon
2017-04-22  4:05 ` bugzilla-daemon
2017-10-06  0:36 ` bugzilla-daemon [this message]
2017-11-22 18:37 ` bugzilla-daemon
2017-11-22 18:41 ` bugzilla-daemon
2017-11-23  8:54 ` bugzilla-daemon
2017-11-23  8:55 ` bugzilla-daemon
2018-01-29 11:06 ` bugzilla-daemon
2018-01-29 11:07 ` bugzilla-daemon
2018-01-29 11:30 ` bugzilla-daemon
2018-02-04 20:03 ` bugzilla-daemon
2018-08-05 17:07 ` bugzilla-daemon
2018-08-06 21:24 ` bugzilla-daemon
2019-11-19  8:15 ` 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-100745-502-VNWpYiVA8T@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox