Created attachment 135429 [details] dmesg of a suspend/resume cycle. When resuming from suspend on my Asus GL702ZC the internal eDP screen does not turn back on, neither does the backlight. External screens (normal DP) are not affected and continue working. I'm running 4.14.0 on this machine. My kernel .config is here in case that is helpful: https://notabug.org/hp/linux-gl702zc/src/master/.config I see the following errors in dmesg: [ 1667.119776] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 1667.119785] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed [ 1667.687497] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed [ 1667.687505] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed When using drm-next-dc the screen does turn on but the system crashes shortly afterwards. I have not been able to get any meaningful debugging data out of that configuration yet. Attached is the full dmesg of the system.
I forgot to mention: I run Fedora 27 in userspace with Xorg. The following package versions may be relevant: xorg-x11-server-Xorg-1.19.5-1.fc27.x86_64 xorg-x11-drv-amdgpu-1.3.0-3.fc27.x86_64 mesa-dri-drivers-17.2.4-1.fc27.x86_64 libdrm-2.4.85-1.fc27.x86_64
This bug could be the same as https://bugs.freedesktop.org/show_bug.cgi?id=103277 - but since I have only one display connected to the GPU - which stays off after resume (and then the system crashes so no other way to look at dmesg output) - I had no chance to see error messages like the ones you reported.
dwagner, these are different issue. This one was reported on a kernel without DC, the other with DC.
-- 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/257.
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.