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: Mon, 05 Jun 2017 10:26:55 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1155792503==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A263789CB3 for ; Mon, 5 Jun 2017 10:26:54 +0000 (UTC) In-Reply-To: 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 --===============1155792503== Content-Type: multipart/alternative; boundary="14966584140.1ae63.24002"; charset="UTF-8" --14966584140.1ae63.24002 Date: Mon, 5 Jun 2017 10:26:54 +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 --- Comment #2 from freedesktop@nuclearsunshine.com --- I've tried with a couple of "distro-friendly" bisection approaches so far b= ut run into problems both times, probably partly due to the relative age of the kernels; I can try vanilla bisection but haven't looked into the details of that yet. Is there anything else I can do that might help identify the problem in the interim, or is bisection the only option? --=20 You are receiving this mail because: You are the assignee for the bug.= --14966584140.1ae63.24002 Date: Mon, 5 Jun 2017 10:26:54 +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

Commen= t # 2 on bug 10129= 0 from freedesktop@nuclearsunshine.com 
I've tried with a couple of "distro-friendly" bisect=
ion approaches so far but
run into problems both times, probably partly due to the relative age of the
kernels; I can try vanilla bisection but haven't looked into the details of
that yet.

Is there anything else I can do that might help identify the problem in the
interim, or is bisection the only option?

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