From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 188091] New: Resume with two monitors, second monitor is not resumed until VT switch
Date: Fri, 18 Nov 2016 10:27:33 +0000 [thread overview]
Message-ID: <bug-188091-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=188091
Bug ID: 188091
Summary: Resume with two monitors, second monitor is not
resumed until VT switch
Product: Drivers
Version: 2.5
Kernel Version: 4.9 rc5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: gwhite@kupulau.com
Regression: No
This is for AMDGPU.
I have an RX470 with two monitors attached via DP. After a long suspend, when
one of the monitors has apparently gone into a deeper sleep state, it takes one
of them longer to wake. When this happens, the second monitor is not detected
and will not be seen until I switch to a VT and then back again. Here's what I
see in dmesg before the switch:
18887.893100] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link
status failed
[18887.893103] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery
failed
[18888.070075] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link
status failed
[18888.070077] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery
failed
Again, after I switch to a VT and then back again, all is well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-18 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 10:27 bugzilla-daemon [this message]
2016-11-21 22:27 ` [Bug 188091] Resume with two monitors, second monitor is not resumed until VT switch bugzilla-daemon
2016-11-21 22:37 ` bugzilla-daemon
2016-11-21 22:37 ` bugzilla-daemon
2016-11-21 22:38 ` bugzilla-daemon
2016-11-22 0:41 ` bugzilla-daemon
2016-11-22 0:43 ` bugzilla-daemon
2016-12-04 0:39 ` bugzilla-daemon
2016-12-04 0:41 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-188091-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.