From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101290] Radeon R9 390X regression - No output (CVT) or corruption (CVT-R) at 4096x2160@60Hz over DisplayPort Date: Sat, 03 Jun 2017 17:21:57 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2006263846==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 18CA06E5BC for ; Sat, 3 Jun 2017 17:21:57 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============2006263846== Content-Type: multipart/alternative; boundary="14965105170.4d21.32657"; charset="UTF-8" --14965105170.4d21.32657 Date: Sat, 3 Jun 2017 17:21:57 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D101290 Bug ID: 101290 Summary: Radeon R9 390X regression - No output (CVT) or corruption (CVT-R) at 4096x2160@60Hz over DisplayPort Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: freedesktop@nuclearsunshine.com I had thought I had filed this bug a long time ago on here, but I can't find it... Graphics card: Radeon R9 390X (Saphhire 11241-04-20G) Display: LG 31MU97 (via DisplayPort) With Linux 4.4.x, 4096 x 2160 @ 60 Hz progressive output was working with standard CVT timing. With Linux 4.5.x onwards, standard CVT timing at that resolution fails (no signal) with the following dmesg output: kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 tr= ies CVT-R timing results in output, but with a flickering/corrupted full-height band down the right hand side (it approximates the intended output, but pix= els seem be to be corrupt in single-pixel horizontal bands and/or flicker in horizontal single-pixel bands) It could be complete coincidence, but the wi= dth of the corrupt band seems to be the difference in width vs. 3840x2160, i.e. aobut 256 pixels. With this timing there are no messages in dmesg. There's a downstream Fedora bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=3D1353341 --=20 You are receiving this mail because: You are the assignee for the bug.= --14965105170.4d21.32657 Date: Sat, 3 Jun 2017 17:21:57 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 101290
Summary Radeon R9 390X regression - No output (CVT) or corruption (CV= T-R) at 4096x2160@60Hz over DisplayPort
Product DRI
Version unspecified
Hardware Other
OS All
Status NEW
Severity major
Priority medium
Component DRM/Radeon
Assignee dri-devel@lists.freedesktop.org
Reporter freedesktop@nuclearsunshine.com 

I had thought I had filed this bug a long time ago on here, bu=
t I can't find
it...

Graphics card: Radeon R9 390X (Saphhire 11241-04-20G)
Display: LG 31MU97 (via DisplayPort)

With Linux 4.4.x, 4096 x 2160 @ 60 Hz progressive output was working wi=
th
standard CVT timing.

With Linux 4.5.x onwards, standard CVT timing at that resolution fails (no
signal) with the following dmesg output:

kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed
kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 tr=
ies

CVT-R timing results in output, but with a flickering/corrupted full-height
band down the right hand side (it approximates the intended output, but pix=
els
seem be to be corrupt in single-pixel horizontal bands and/or flicker in
horizontal single-pixel bands) It could be complete coincidence, but the wi=
dth
of the corrupt band seems to be the difference in width vs. 3840x2160, i.e.
aobut 256 pixels. With this timing there are no messages in dmesg.

There's a downstream Fedora bug report here:
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D1353341

You are receiving this mail because:
  • You are the assignee for the bug.
= --14965105170.4d21.32657-- --===============2006263846== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============2006263846==--