Bug 100675 - No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed
Summary: No signal on DisplayPort [drm:radeon_dp_link_train [radeon]] *ERROR* displayp...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-13 19:55 UTC by Oleg Höfling
Modified: 2019-11-19 09:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg log (65.72 KB, text/plain)
2017-04-13 19:55 UTC, Oleg Höfling 		no flags Details
View All

Description Oleg Höfling 2017-04-13 19:55:02 UTC 
Created attachment 130835 [details]
dmesg log

First of all, this is the first bug reported by me, so I apologize in advance 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 detected" 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
Comment 1 Martin Peres 2019-11-19 09:27:50 UTC 
-- 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/792.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.