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: Thu, 03 Oct 2019 16:40:14 +0000	[thread overview]
Message-ID: <bug-107731-502-Nmd6nZsoTd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107731-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from James Wood <Chryseus8080@gmail.com> ---
I was about to report having the same bug but it seems the today's Mesa
19.2.0-2 update has solved the problem, I will include what I was originally
going to post in case it's of use to anyone.

---

I've began to have this bug in the last week or two, I have two monitors one an
Asus PA238 connected via DVI has no issues, the other a AOC 2270W connected via
DP changes to a lower resolution after wakeup, typically 800x600 which cannot
be changed back to normal.

I can reproduce this consistently by using 'xset -display :0 dpms force
standby' and waiting about one minute.
Running 'xrandr --output DisplayPort-2 --auto' restores the display to its
normal native resolution.

The system log shows the following error:
[drm] enabling link 2 failed: 15
[drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state
failed with -22
Stack trace: https://pastebin.com/yguN5NUk

System specification:
OS: Arch linux 5.3.1-arch1-1-ARCH
GPU: AMD Radeon RX 590 using AMDGPU-Pro
DE: KDE Plasma 5.16.5

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

[-- Attachment #1.2: Type: text/html, Size: 2158 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-10-03 16:40 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
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 [this message]
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-Nmd6nZsoTd@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.