From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 188091] Resume with two monitors, second monitor is not resumed until VT switch
Date: Tue, 22 Nov 2016 00:43:30 +0000 [thread overview]
Message-ID: <bug-188091-2300-mUqbk9vFMU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-188091-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=188091
--- Comment #6 from Vedran Miletić <vedran@miletic.net> ---
(In reply to Greg White from comment #5)
> I should also note this is easily reproducible but still intermittent. I'd
> say 80% of the time, I see this. It's also not always one monitor - it can
> be either of them.
Interesting. I have a very similar issue on Fiji (bug 176311) with two DP
monitors, but in case of Fiji it is always one monitor that will be blank until
the VT switch happens. And the error message is different.
--
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 prev parent reply other threads:[~2016-11-22 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 10:27 [Bug 188091] New: Resume with two monitors, second monitor is not resumed until VT switch bugzilla-daemon
2016-11-21 22:27 ` [Bug 188091] " 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 [this message]
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-mUqbk9vFMU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).