Bug 104205

Summary:

displayport connected monitor doesn't initialize display

Product:

DRI

Reporter:

Bret Towe <magnade>

Component:

DRM/AMDgpu

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED MOVED

QA Contact:

Severity:

normal

Priority:

medium

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
dmesg log	none
dmesg with working screen	none

Description Bret Towe 2017-12-11 02:31:14 UTC

I have a LG 29UB55-B 21:9 monitor connected via DisplayPort to a Radeon R7 370 card
after boot when xorg loads 99% of the time the monitor won't see a signal and goes to sleep
once its woken back up by its power button it sees the normal screen at its native res of 2560x1080

I also see I assume the same problem if i change resolution down to 1920x1080 its fine but switch back to 2560x1080 and screen goes to sleep with no signal
wake it back up and fine again at 2560

I see the below in dmesg:

[    6.400479] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
[    6.400523] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed

kernel is 4.14.4 currently it's been going on since I got the monitor
I don't recall what version that was.

xorg is on 1.19.5
amdgpu driver is 1.4.0
also tried the radeon driver and acts same
haven't tried binary drivers

no errors in xorg log

Comment 1 Michel Dänzer 2017-12-11 11:11:58 UTC

Please attach the full dmesg output.

It might be worth trying a current 4.15-rc kernel with CONFIG_DRM_AMD_DC and CONFIG_DRM_AMD_DC_PRE_VEGA enabled.

Comment 2 Bret Towe 2017-12-16 20:34:11 UTC

Created attachment 136229 [details]
dmesg log

Comment 3 Bret Towe 2017-12-16 23:59:34 UTC

Created attachment 136234 [details]
dmesg with working screen

here is dmesg on a boot that brought up monitor correctly
version is:
Linux ghoststar 4.15.0-rc3-mainline #1 SMP PREEMPT Sat Dec 16 15:27:26 PST 2017 x86_64 GNU/Linux

I'm not sure if this version fixed it yet since a reboot onto 4.14.x worked also
seems like cold boot might cause it to happen more often?
ill try this a few more times over the coming week and see if it behaves and report back

Comment 4 Bret Towe 2017-12-17 15:10:59 UTC

4.15-rc3 still has the problem

Comment 5 Harry Wentland 2017-12-20 23:33:51 UTC

Do you have a chance to try enabling the two config options Michel mentioned and see if this changes things? We have a new display driver in 4.15 (AMD_DC) that could very well make a difference here.

Comment 6 Bret Towe 2017-12-20 23:38:20 UTC

maybe it wasn't clear but I tested rc3 with those options and it still has the issue

Comment 7 Martin Peres 2019-11-19 08:26:46 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/269.

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.