All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle)
Date: Sun, 10 Mar 2019 07:44:28 +0000	[thread overview]
Message-ID: <bug-107731-502-NZAQkAZFO7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107731-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107731

--- Comment #1 from L.S.S. <ragnaros39216@yandex.com> ---
Having similar issues with Manjaro Linux (4.20 Kernel) and AMD video cards.

I've a 4K@60Hz capable monitor (Lenovo ThinkVision P27) and an ATEN CS1924 KVM
behind it (as I need to use this monitor for 4 different PCs). I've two PCs
with Manjaro Linux and AMD GPU, and I can 100% reproduce the issue on both of
them.

This happens whenever I power off the monitor (or when it went idle). After
powering the monitor back on, it reverts to a lower resolution (During most
cases, xrandr reported max 2048x1536 but it actually picked 1792x1344. Recently
I also noticed sometimes xrandr would report only 800x600).

It can be fixed by switching the input channel back and forth on the KVM (which
I think is equivalent to unplugging and replugging the DP port).

On one of the PCs, it used to have an nVidia video card before replacing it
with Radeon VII. With an nVidia video card, this issue did not occur (using
same configuration).

When this happens, I can find this red line in dmesg. Other log entries are
mostly about on-monitor USB hubs and such, and they're irrelevent to the issue
from the look of it.

[drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state
failed with -22

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2302 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

  parent reply	other threads:[~2019-03-10  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  1:37 [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle) bugzilla-daemon
2018-08-29  1:38 ` bugzilla-daemon
2019-03-10  7:44 ` bugzilla-daemon [this message]
2019-03-10  7:48 ` bugzilla-daemon
2019-03-10  7:56 ` bugzilla-daemon
2019-03-11 16:07 ` bugzilla-daemon
2019-03-17  8:08 ` bugzilla-daemon
2019-03-18 20:08 ` bugzilla-daemon
2019-03-19 10:52 ` bugzilla-daemon
2019-03-19 13:50 ` bugzilla-daemon
2019-03-19 18:27 ` bugzilla-daemon
2019-03-19 19:18 ` bugzilla-daemon
2019-03-22 17:28 ` bugzilla-daemon
2019-05-22  0:58 ` bugzilla-daemon
2019-05-22  2:20 ` bugzilla-daemon
2019-10-03 16:40 ` bugzilla-daemon
2019-11-19  8:50 ` 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-107731-502-NZAQkAZFO7@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 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.