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, 17 Mar 2019 08:08:28 +0000 [thread overview]
Message-ID: <bug-107731-502-lQUpR1WwJ9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107731-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107731
L.S.S. <ragnaros39216@yandex.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ragnaros39216@yandex.com
--- Comment #5 from L.S.S. <ragnaros39216@yandex.com> ---
Created attachment 143701
--> https://bugs.freedesktop.org/attachment.cgi?id=143701&action=edit
Logs with drm.debug=4. Looks like some DC validation failure.
It seems when I power cycle the monitor, I get some "failed DC validation"
errors. As for link training failure... yeah, just looked at the log and it did
mention something like that.
I just upgraded my Linux systems to 5.0 kernel, and the problem persists there.
The log is also done with 5.0 kernel on one of the systems.
The problem seems to be amdgpu/DC related as my Linux systems have AMD cards of
different generations and are all affected by the issue (and 100%
reproducible).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2815 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
next prev parent reply other threads:[~2019-03-17 8:08 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 [this message]
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-lQUpR1WwJ9@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.