From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100675] No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed Date: Thu, 13 Apr 2017 19:55:02 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0549954301==" 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 902B66E90E for ; Thu, 13 Apr 2017 19:55:03 +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 --===============0549954301== Content-Type: multipart/alternative; boundary="14921133020.dEB2A6c83.7278"; charset="UTF-8" --14921133020.dEB2A6c83.7278 Date: Thu, 13 Apr 2017 19:55:02 +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=3D100675 Bug ID: 100675 Summary: No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: oleg.hoefling@gmail.com Created attachment 130835 --> https://bugs.freedesktop.org/attachment.cgi?id=3D130835&action=3Dedit dmesg log First of all, this is the first bug reported by me, so I apologize in advan= ce if I assigned it to a wrong category. I have a monitor, a DisplayPort cable= and two notebooks. When the monitor is connected to the first notebook (Lenovo T440), everything works fine, so the cable seems is working fine. Now, when= the monitor is connected to the second notebook, it shows "no signal is detecte= d" and switches into sleep mode. Here is what dmesg outputs (I will attach the complete dmesg log): [ 12.064503] [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [ 12.064517] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed Of course, after logging into the X session, the monitor remains black, although Xorg does not report any errors in log: $ grep -n EE /var/log/Xorg.0.log 16: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. System: Linux msi_gx70 4.10.9-gentoo #2 SMP Thu Apr 13 21:30:04 CEST 2017 x86_64 AMD A10-5750M APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux --=20 You are receiving this mail because: You are the assignee for the bug.= --14921133020.dEB2A6c83.7278 Date: Thu, 13 Apr 2017 19:55:02 +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 100675
Summary No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] = *ERROR* displayport link status failed
Product DRI
Version unspecified
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component DRM/Radeon
Assignee dri-devel@lists.freedesktop.org
Reporter oleg.hoefling@gmail.com 

Created attachment 130835 [deta=
ils]
dmesg log

First of all, this is the first bug reported by me, so I apologize in advan=
ce
if I assigned it to a wrong category. I have a monitor, a DisplayPort cable=
 and
two notebooks. When the monitor is connected to the first notebook (Lenovo
T440), everything works fine, so the cable seems is working fine. Now, when=
 the
monitor is connected to the second notebook, it shows "no signal is de=
tected"
and switches into sleep mode. Here is what dmesg outputs (I will attach the
complete dmesg log):

[   12.064503] [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link
status failed
[   12.064517] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery
failed

Of course, after logging into the X session, the monitor remains black,
although Xorg does not report any errors in log:

$ grep -n EE /var/log/Xorg.0.log
16:     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

System:

Linux msi_gx70 4.10.9-gentoo #2 SMP Thu Apr 13 21:30:04 CEST 2017 x86_64 AMD
A10-5750M APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux

You are receiving this mail because:
  • You are the assignee for the bug.
= --14921133020.dEB2A6c83.7278-- --===============0549954301== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0549954301==--