All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208893] New: Navi (RX 5700 XT) system appears to hang with more than one display connected
Date: Thu, 13 Aug 2020 05:33:21 +0000	[thread overview]
Message-ID: <bug-208893-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 208893
           Summary: Navi (RX 5700 XT) system appears to hang with more
                    than one display connected
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.8.1, 5.7.15
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: gordon@gordonite.tech
        Regression: No

I am using Fedora 32, and have tried the latest fixes with 5.8.1 mainline, and
stable Fedora 32.

If i connect a single monitor to my system it works fine.

However, when I connect a freesync monitor (144Hz and another 24 inch monitor,
the system during boot shows much larger startup times, and also general
hanging, the screen flickers too but ONLY when the second monitor is
connected.)

When I boot the system, even the 'booting' is delayed considerably by
comparison when the second display port monitor is connected.

It seems to be one of two problems:
- with multiple displays the card is not behaving properly
- the difference in refresh rates is causing a problem / conflict.

I do not know for certain where the problem lies, but even booting is slowing
down so I do not believe this is purely a Mesa issue.

Using wayland or xorg seems to make little difference the problem is on both,
and even on terminal sessions (slowing down terminal output to the display and
general unresponsiveness)

however as stated above, rebooting with a single display resolves these
problems.

-- 
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-08-13  5:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  5:33 bugzilla-daemon [this message]
2020-08-13  5:58 ` [Bug 208893] Navi (RX 5700 XT) system appears to hang with more than one display connected bugzilla-daemon
2020-08-13  6:01 ` bugzilla-daemon
2020-08-13  6:02 ` bugzilla-daemon
2020-08-13  6:39 ` bugzilla-daemon
2020-08-13  6:39 ` bugzilla-daemon
2020-08-13  6:47 ` bugzilla-daemon
2020-08-13  6:47 ` bugzilla-daemon
2020-08-13  6:48 ` bugzilla-daemon
2020-08-13  6:51 ` bugzilla-daemon
2020-08-13 15:34 ` bugzilla-daemon
2020-08-13 17:30 ` bugzilla-daemon
2020-08-13 19:16 ` bugzilla-daemon
2020-08-20 13:45 ` bugzilla-daemon
2020-08-21 14:33 ` bugzilla-daemon
2020-09-01  1:13 ` bugzilla-daemon
2020-09-12 21:29 ` bugzilla-daemon
2020-09-13 12:50 ` bugzilla-daemon
2020-09-13 13:03 ` bugzilla-daemon
2020-09-13 13:17 ` 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-208893-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.