Bug 108843

Summary: Laptop with ATI RX 580 doesn't turn the screen on when resuming.
Product: DRI Reporter: alex14641
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium    
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg
none
Kernel config file
none
dmesg with amdgpu.dc=1 none

Description alex14641 2018-11-23 01:11:51 UTC
Created attachment 142582 [details]
dmesg

When I close the laptop lid, the screen turns off, and the following appears in dmesg:
 
[ 5802.486819] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[ 5802.486840] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
[ 5803.077555] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
[ 5803.077576] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed


When I open the lid, the screen stays blank. I'm running Slackware Current with a kernel built from drm-next-4.21-wip.
Comment 1 alex14641 2018-11-23 01:13:19 UTC
Created attachment 142583 [details]
Kernel config file
Comment 2 Michel Dänzer 2018-11-23 08:25:25 UTC
Does amdgpu.dc=1 on the kernel command line help?
Comment 3 alex14641 2018-11-23 16:16:41 UTC
It doesn't help. In addition, the screen goes blank when KMS is engaged.
Comment 4 alex14641 2018-11-23 16:17:38 UTC
Created attachment 142595 [details]
dmesg with amdgpu.dc=1
Comment 5 alex14641 2018-11-23 16:34:53 UTC
Correction: due to the screen going blank during boot, I didn't test closing the lid.
Comment 6 alex14641 2018-11-27 01:47:40 UTC
Just tried with the latest from wip: problem persists.
Comment 7 alex14641 2018-12-20 21:58:42 UTC
Tried with wip from 12/19 and dc=1: display now turns on when laptop is opened, and the error messages no longer appear.
Comment 8 Martin Peres 2019-11-19 09:05:16 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/617.

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.