From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107978] [amdgpu] Switching to tty fails with DisplayPort 1.2 monitor going to sleep (REG_WAIT timeout / dce110_stream_encoder_dp_blank)
Date: Mon, 14 Jan 2019 02:01:40 +0000 [thread overview]
Message-ID: <bug-107978-502-IlnSB0oOPb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107978-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #41 from Shmerl <shtetldik@gmail.com> ---
Same thing still happen with 5.0-rc2. Does anyone else experience this race
condition when the monitor goes to sleep right after boot? It is related to the
same setup (DisplayPort 1.2), since it's not happening with it disabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1354 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-14 2:01 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 13:01 [Bug 107978] [amdgpu] Switching to tty fails with DisplayPort monitor going to sleep (REG_WAIT timeout / dce110_stream_encoder_dp_blank) bugzilla-daemon
2018-09-20 3:10 ` bugzilla-daemon
2018-10-05 0:18 ` bugzilla-daemon
2018-10-05 15:59 ` bugzilla-daemon
2018-10-07 19:20 ` bugzilla-daemon
2018-10-07 19:23 ` bugzilla-daemon
2018-10-09 13:18 ` bugzilla-daemon
2018-10-09 13:57 ` bugzilla-daemon
2018-10-09 13:58 ` bugzilla-daemon
2018-10-11 14:17 ` bugzilla-daemon
2018-10-11 16:26 ` bugzilla-daemon
2018-10-11 16:41 ` [Bug 107978] [amdgpu] Switching to tty fails with DisplayPort 1.2 " bugzilla-daemon
2018-10-11 16:55 ` bugzilla-daemon
2018-10-16 22:42 ` bugzilla-daemon
2018-10-17 13:07 ` bugzilla-daemon
2018-10-17 13:10 ` bugzilla-daemon
2018-10-21 23:30 ` bugzilla-daemon
2018-11-13 16:54 ` bugzilla-daemon
2018-11-22 18:55 ` bugzilla-daemon
2018-12-03 19:16 ` bugzilla-daemon
2018-12-03 19:30 ` bugzilla-daemon
2018-12-06 20:35 ` bugzilla-daemon
2018-12-06 21:47 ` bugzilla-daemon
2018-12-06 21:48 ` bugzilla-daemon
2018-12-06 21:51 ` bugzilla-daemon
2018-12-06 21:56 ` bugzilla-daemon
2018-12-07 6:30 ` bugzilla-daemon
2018-12-07 6:32 ` bugzilla-daemon
2018-12-07 14:58 ` bugzilla-daemon
2018-12-17 3:46 ` bugzilla-daemon
2018-12-17 15:46 ` bugzilla-daemon
2018-12-17 15:49 ` bugzilla-daemon
2018-12-17 15:54 ` bugzilla-daemon
2018-12-17 16:09 ` bugzilla-daemon
2018-12-17 16:27 ` bugzilla-daemon
2018-12-17 16:27 ` bugzilla-daemon
2018-12-18 1:37 ` bugzilla-daemon
2018-12-18 2:00 ` bugzilla-daemon
2018-12-18 15:02 ` bugzilla-daemon
2018-12-18 16:22 ` bugzilla-daemon
2018-12-25 2:21 ` bugzilla-daemon
2018-12-27 8:14 ` bugzilla-daemon
2019-01-07 2:05 ` bugzilla-daemon
2019-01-07 4:25 ` bugzilla-daemon
2019-01-14 2:01 ` bugzilla-daemon [this message]
2019-01-15 15:56 ` bugzilla-daemon
2019-01-24 16:03 ` bugzilla-daemon
2019-01-24 17:59 ` bugzilla-daemon
2019-01-24 19:09 ` bugzilla-daemon
2019-01-24 21:49 ` bugzilla-daemon
2019-01-25 2:08 ` bugzilla-daemon
2019-01-25 16:14 ` bugzilla-daemon
2019-01-25 16:17 ` bugzilla-daemon
2019-01-25 16:18 ` bugzilla-daemon
2019-01-25 16:24 ` bugzilla-daemon
2019-01-28 15:16 ` bugzilla-daemon
2019-01-28 16:36 ` bugzilla-daemon
2019-01-28 17:59 ` bugzilla-daemon
2019-01-28 18:01 ` bugzilla-daemon
2019-02-18 17:48 ` bugzilla-daemon
2019-02-18 17:52 ` bugzilla-daemon
2019-02-18 21:00 ` bugzilla-daemon
2019-02-22 19:43 ` bugzilla-daemon
2019-05-07 23:46 ` 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-107978-502-IlnSB0oOPb@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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).