All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202799] New: amd/dc: right monitor sometimes never comes back up on dual-display setup after locking session
Date: Thu, 07 Mar 2019 02:20:56 +0000	[thread overview]
Message-ID: <bug-202799-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 202799
           Summary: amd/dc: right monitor sometimes never comes back up on
                    dual-display setup after locking session
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.0
          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: libcg@protonmail.com
        Regression: No

Created attachment 281547
  --> https://bugzilla.kernel.org/attachment.cgi?id=281547&action=edit
xrandr --props output

- linux 5.0 (4.20 also had the same issue)
- xf86-video-amdgpu 18.1.0
- GNOME 3.30

Left screen is a Dell U2412M (1920x1200), right screen is a Dell P2715Q (4K
monitor set at 2560x1440, primary). GPU is RX 580.

Steps to reproduce:
- Lock session, screens turn off
- After a while, press a key to turn the screens back on again
- When the left screen lights up first, the system only displays an image on
the left screen. The right screen lights up afterwards but goes back to sleep
because it's getting no signal, although xrandr still recognizes it.  I need to
manually turn off the right screen and back on again to get it to reconfigure.

When using `amdgpu.dc=0`, this issue disappears.

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

             reply	other threads:[~2019-03-07  2:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  2:20 bugzilla-daemon [this message]
2019-03-07  9:19 ` [Bug 202799] amd/dc: right monitor sometimes never comes back up on dual-display setup after locking session bugzilla-daemon
2019-03-07 21:21 ` bugzilla-daemon
2019-03-07 21:27 ` bugzilla-daemon
2019-03-13 22:02 ` bugzilla-daemon
2019-03-14  8:56 ` bugzilla-daemon
2019-03-14 13:14 ` bugzilla-daemon
2019-03-15 22:00 ` bugzilla-daemon
2019-03-28  3:47 ` bugzilla-daemon
2019-05-10 20:15 ` bugzilla-daemon
2019-07-09 23:04 ` bugzilla-daemon
2020-02-15 22:44 ` 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-202799-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.