From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109246] HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1
Date: Mon, 05 Aug 2019 19:00:34 +0000 [thread overview]
Message-ID: <bug-109246-502-ezQiqfano7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109246-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 773 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #23 from Tom reed <tom@reed.vg> ---
Confirmed problem. Dual monitors prevent DPMS power off.
Problem happens when triggered by screen off or manually with xset dpms force
off.
GPU is Gigabyte RX580.
Ubuntu 18.04 LTS. Kernel 5.0.
Monitors are 2 Dell S2719dc.
Problem occurs on xorg and on Wayland.
Problem occurs connected to HDMI and display port, and also with dual display
port.
A workaround is to disable auto input switching on the monitors. This solves
the problem.
Appears that when one monitor is switching inputs after turning off it wakes up
the other monitor. A race condition between the two.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1605 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 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-08-05 19:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 5:09 [Bug 109246] HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1 bugzilla-daemon
2019-01-08 5:23 ` bugzilla-daemon
2019-01-08 8:02 ` bugzilla-daemon
2019-01-08 9:11 ` bugzilla-daemon
2019-01-08 12:58 ` bugzilla-daemon
2019-01-08 14:29 ` bugzilla-daemon
2019-01-08 17:13 ` bugzilla-daemon
2019-01-08 17:15 ` bugzilla-daemon
2019-01-08 18:07 ` bugzilla-daemon
2019-01-08 19:12 ` bugzilla-daemon
2019-01-08 20:20 ` bugzilla-daemon
2019-01-09 5:12 ` bugzilla-daemon
2019-01-09 9:32 ` bugzilla-daemon
2019-01-09 14:39 ` bugzilla-daemon
2019-01-19 5:52 ` bugzilla-daemon
2019-01-25 18:50 ` bugzilla-daemon
2019-02-18 1:56 ` bugzilla-daemon
2019-02-25 3:36 ` bugzilla-daemon
2019-02-25 5:27 ` bugzilla-daemon
2019-03-14 2:44 ` bugzilla-daemon
2019-03-25 20:38 ` bugzilla-daemon
2019-05-15 3:48 ` bugzilla-daemon
2019-07-09 4:14 ` bugzilla-daemon
2019-08-05 19:00 ` bugzilla-daemon [this message]
2019-08-14 8:58 ` bugzilla-daemon
2019-08-25 6:42 ` bugzilla-daemon
2019-09-04 8:21 ` bugzilla-daemon
2019-09-09 14:21 ` bugzilla-daemon
2019-09-21 17:29 ` bugzilla-daemon
2019-09-23 9:30 ` bugzilla-daemon
2019-11-19 9:10 ` 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-109246-502-ezQiqfano7@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).