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: Thu, 20 Oct 2016 17:16:03 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1732521215==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id A07546EBE1 for ; Thu, 20 Oct 2016 17:16:03 +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 --===============1732521215== Content-Type: multipart/alternative; boundary="14769837631.02d2b.7722"; charset="UTF-8" --14769837631.02d2b.7722 Date: Thu, 20 Oct 2016 17:16:03 +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 #38 from Yves W. --- (In reply to Jan Niklas Hasse from comment #37) > > Sorry, but I don't know what you mean by "using bitsect". >=20 > Changes to the source code of the driver are controlled via Git as commit= s. > 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 section= ing > the pool of possible first bad commits in two sections repeatedly). >=20 > I'm not sure though that this good commit exists though. Flickering also > happens with 4.4 for me. means i have to try manually each step and recompile kernel? But that will = take ages :) I don't have that much time. btw mint 18 kernel updated to 4.4.0-43-generic It's still working like charm with 144hz @ 1440p - no flickering .. :) --=20 You are receiving this mail because: You are the assignee for the bug.= --14769837631.02d2b.7722 Date: Thu, 20 Oct 2016 17:16:03 +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 # 38 on bug 93826<= /a> from = Yves W. 
(In reply to Jan Niklas Hasse from comment #37)
> > Sorry, but I don't know what you mean by &q=
uot;using bitsect".
>=20
> Changes to the source code of the driver are controlled via Git as com=
mits.
> Assuming it once worked 144 Hz it's possible to use Git to find out wh=
ich
> commit caused the flickering. This is done by identifying any commit w=
hich
> 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 sect=
ioning
> the pool of possible first bad commits in two sections repeatedly).
>=20
> I'm not sure though that this good commit exists though. Flickering al=
so
> happens with 4.4 for me.

means i have to try manually each step and recompile kernel? But that will =
take
ages :) I don't have that much time.

btw mint 18 kernel updated to 4.4.0-43-generic
It's still working like charm with 144hz @ 1440p - no flickering .. :)<=
/pre>

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