All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210429] New: AMDGPU - DRM connector force-probe after DPMS causes monitor to reconnect
Date: Mon, 30 Nov 2020 17:50:28 +0000	[thread overview]
Message-ID: <bug-210429-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 210429
           Summary: AMDGPU - DRM connector force-probe after DPMS causes
                    monitor to reconnect
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.4.80
          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: jordanleppert@gmail.com
        Regression: No

This is with a Vega64 card, connected to two monitors via DisplayPort 1.2.

When the connector is force-probed with a call to drmModeGetConnector, this is
causing the connection to the monitor to disconnect, and reconnect.

I'm seeing this issue using Wayland, specifically a wlroots based compositor.
This patch to wlroots (which unfortunately needs to be reverted) stopped the
problem happening: https://github.com/swaywm/wlroots/pull/2482/files

-- 
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:[~2020-11-30 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 17:50 bugzilla-daemon [this message]
2020-11-30 18:56 ` [Bug 210429] AMDGPU - DRM connector force-probe after DPMS causes monitor to reconnect bugzilla-daemon
2020-12-22 17:16 ` bugzilla-daemon
2023-09-27 12:57 ` 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-210429-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.