From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate Date: Wed, 19 Oct 2016 21:07:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1862182670==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CF97F6E9D0 for ; Wed, 19 Oct 2016 21:07:29 +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 --===============1862182670== Content-Type: multipart/alternative; boundary="14769112490.f90c.17718"; charset="UTF-8" --14769112490.f90c.17718 Date: Wed, 19 Oct 2016 21:07:29 +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=3D93826 --- Comment #37 from Jan Niklas Hasse --- > Sorry, but I don't know what you mean by "using bitsect". Changes to the source code of the driver are controlled via Git as commits. Assuming it once worked 144 Hz it's possible to use Git to find out which commit caused the flickering. This is done by identifying any commit which worked (good, in your case 4.4) and a commit which doesn't work (bad, 4.8). Bisecting will then help you find the first bad commit faster (by sectioning the pool of possible first bad commits in two sections repeatedly). I'm not sure though that this good commit exists though. Flickering also happens with 4.4 for me. --=20 You are receiving this mail because: You are the assignee for the bug.= --14769112490.f90c.17718 Date: Wed, 19 Oct 2016 21:07:29 +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 # 37 on bug 93826<= /a> from Jan Niklas Hasse 
> Sorry, but I don't know what you me=
an by "using bitsect".

Changes to the source code of the driver are controlled via Git as commits.
Assuming it once worked 144 Hz it's possible to use Git to find out which
commit caused the flickering. This is done by identifying any commit which
worked (good, in your case 4.4) and a commit which doesn't work (bad, 4.8).
Bisecting will then help you find the first bad commit faster (by sectioning
the pool of possible first bad commits in two sections repeatedly).

I'm not sure though that this good commit exists though. Flickering also
happens with 4.4 for me.

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