From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105300] amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock
Date: Fri, 02 Mar 2018 13:40:50 +0000 [thread overview]
Message-ID: <bug-105300-502-3mmcFkakFi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105300-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #8 from tempel.julian@gmail.com ---
Video which shows the artifacts:
https://youtu.be/it3d6BjpZjU
(can also be quite worse when doing stuff)
It happens with every desktop environment with and without enabled OGL
compositor. In the video, it's KDE Plasma on Xorg.
But there is no difference with a Wayland session, the artifacts there are the
same.
You are correct that the display's own edid information doesn't know any other
refreshrate than 59.95Hz.
However, these Korean import display's are very often used with higher
refreshrates because their panels allow this without incompatible scaler in
between. With the old display stack, I can even set 85Hz without any issues.
75Hz is also not very uncommon for some 2560x1440p IPS displays, I suppose
there is the realistic possibility that also displays which have a 2560x1440
75Hz resolution in their original edid are affected by this bug (since the old
stack isn't affected, I'm quite sure it's some kind of bug).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2087 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-02 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:28 [Bug 105300] amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock bugzilla-daemon
2018-03-01 15:06 ` bugzilla-daemon
2018-03-01 17:21 ` bugzilla-daemon
2018-03-01 19:43 ` bugzilla-daemon
2018-03-01 20:26 ` bugzilla-daemon
2018-03-02 13:36 ` bugzilla-daemon
2018-03-02 13:37 ` bugzilla-daemon
2018-03-02 13:38 ` bugzilla-daemon
2018-03-02 13:40 ` bugzilla-daemon [this message]
2018-03-02 15:03 ` bugzilla-daemon
2018-03-02 15:41 ` bugzilla-daemon
2018-03-29 14:05 ` bugzilla-daemon
2018-04-23 13:03 ` bugzilla-daemon
2018-04-23 13:04 ` bugzilla-daemon
2018-06-05 16:31 ` bugzilla-daemon
2018-10-31 18:58 ` bugzilla-daemon
2018-10-31 19:08 ` 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-105300-502-3mmcFkakFi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox