dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197925] [amdgpu_dc][carrizo] multiple monitor handling errors
Date: Sat, 02 Dec 2017 02:37:30 +0000	[thread overview]
Message-ID: <bug-197925-2300-XgS9ofaIqk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197925-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=197925

--- Comment #5 from kwkaess@gmx.com ---
Half fixes #2:

On first idle and resume from idle after boot, everything works. Internal
monitor backlight shuts off, both screens turn back on. The second time, the
internal backlight stays on upon entering idle, and neither monitor turns back
on at resume from idle.

-- 
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

  parent reply	other threads:[~2017-12-02  2:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 18:30 [Bug 197925] New: [amdgpu_dc][carrizo] multiple monitor handling errors bugzilla-daemon
2017-11-21 20:09 ` [Bug 197925] " bugzilla-daemon
2017-11-28  9:31 ` bugzilla-daemon
2017-12-01 18:50 ` bugzilla-daemon
2017-12-01 23:26 ` bugzilla-daemon
2017-12-02  2:37 ` bugzilla-daemon [this message]
2017-12-02 10:45 ` bugzilla-daemon
2017-12-03 23:00 ` bugzilla-daemon
2017-12-15 22:41 ` bugzilla-daemon
2017-12-16  2:15 ` bugzilla-daemon
2017-12-18 10:18 ` bugzilla-daemon
2017-12-20  9:34 ` bugzilla-daemon
2018-02-07 20:14 ` bugzilla-daemon
2018-02-27  0:48 ` bugzilla-daemon
2018-03-10 21:50 ` bugzilla-daemon
2018-03-12 13:32 ` bugzilla-daemon
2018-03-12 19:28 ` 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-197925-2300-XgS9ofaIqk@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).