From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0557102711==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 1AAE76E8C0 for ; Fri, 6 Oct 2017 00:36:30 +0000 (UTC) In-Reply-To: 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 --===============0557102711== Content-Type: multipart/alternative; boundary="15072501901.160a.9782"; charset="UTF-8" --15072501901.160a.9782 Date: Fri, 6 Oct 2017 00:36:30 +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=3D100745 Eddie Ringle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eddie@ringle.io --- Comment #6 from Eddie Ringle --- Wanted to add that I'm seeing this issue now under a similar setup. I've se= en it in the past, but the last few kernel releases have been pretty smooth. O= nce 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 sle= ep 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --15072501901.160a.9782 Date: Fri, 6 Oct 2017 00:36:30 +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 Eddie Ringle changed bug 10074= 5
What Removed Added
CC   eddie@ringle.io

Commen= t # 6 on bug 10074= 5 from Eddie Ringle 
Wanted to add that I'm seeing this issue now under a similar s=
etup. I've seen
it in the past, but the last few kernel releases have been pretty smooth. O=
nce
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 fa=
iled" 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 sle=
ep
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.
= --15072501901.160a.9782-- --===============0557102711== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0557102711==--