From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate
Date: Wed, 19 Oct 2016 21:07:30 +0000 [thread overview]
Message-ID: <bug-93826-502-rOdAFpHaMN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93826-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #37 from Jan Niklas Hasse <jhasse@gmail.com> ---
> 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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1653 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:[~2016-10-19 21:07 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 18:29 [Bug 93826] 144Hz graphic glitches and bad resolution bugzilla-daemon
2016-01-22 18:30 ` bugzilla-daemon
2016-01-22 18:31 ` bugzilla-daemon
2016-01-22 18:32 ` bugzilla-daemon
2016-01-22 18:32 ` bugzilla-daemon
2016-01-22 18:33 ` bugzilla-daemon
2016-01-22 18:34 ` bugzilla-daemon
2016-01-22 18:35 ` bugzilla-daemon
2016-01-22 18:36 ` bugzilla-daemon
2016-01-22 18:36 ` bugzilla-daemon
2016-01-22 18:37 ` [Bug 93826] 144Hz graphic glitches and bad refresh rate bugzilla-daemon
2016-01-22 18:41 ` bugzilla-daemon
2016-01-22 18:41 ` bugzilla-daemon
2016-01-22 18:42 ` bugzilla-daemon
2016-01-22 18:42 ` bugzilla-daemon
2016-01-23 23:23 ` bugzilla-daemon
2016-01-25 7:27 ` bugzilla-daemon
2016-01-25 8:39 ` bugzilla-daemon
2016-02-24 17:25 ` bugzilla-daemon
2016-02-27 14:05 ` bugzilla-daemon
2016-02-27 14:11 ` bugzilla-daemon
2016-02-29 22:42 ` bugzilla-daemon
2016-02-29 22:59 ` bugzilla-daemon
2016-03-01 7:12 ` bugzilla-daemon
2016-05-12 18:11 ` bugzilla-daemon
2016-05-23 11:17 ` bugzilla-daemon
2016-05-23 11:31 ` bugzilla-daemon
2016-05-24 16:21 ` bugzilla-daemon
2016-06-19 16:28 ` bugzilla-daemon
2016-07-06 16:28 ` bugzilla-daemon
2016-10-09 7:11 ` bugzilla-daemon
2016-10-09 7:15 ` bugzilla-daemon
2016-10-09 7:16 ` [Bug 93826] 2560x1440 @144Hz " bugzilla-daemon
2016-10-12 9:03 ` bugzilla-daemon
2016-10-12 13:34 ` bugzilla-daemon
2016-10-13 17:41 ` bugzilla-daemon
2016-10-14 1:16 ` bugzilla-daemon
2016-10-14 18:50 ` bugzilla-daemon
2016-10-15 6:30 ` bugzilla-daemon
2016-10-19 11:07 ` bugzilla-daemon
2016-10-19 11:11 ` bugzilla-daemon
2016-10-19 21:07 ` bugzilla-daemon [this message]
2016-10-20 17:16 ` bugzilla-daemon
2016-10-21 11:12 ` bugzilla-daemon
2016-12-07 20:06 ` bugzilla-daemon
2016-12-08 0:53 ` bugzilla-daemon
2016-12-08 0:54 ` bugzilla-daemon
2016-12-08 17:51 ` bugzilla-daemon
2016-12-10 1:28 ` bugzilla-daemon
2017-04-26 23:14 ` bugzilla-daemon
2017-05-11 9:46 ` bugzilla-daemon
2017-05-22 14:34 ` bugzilla-daemon
2017-05-22 14:55 ` bugzilla-daemon
2017-05-22 16:23 ` bugzilla-daemon
2017-05-23 11:29 ` bugzilla-daemon
2017-05-29 9:32 ` bugzilla-daemon
2017-06-07 15:36 ` bugzilla-daemon
2017-06-07 16:41 ` bugzilla-daemon
2017-06-07 19:04 ` bugzilla-daemon
2017-06-08 1:46 ` bugzilla-daemon
2017-06-11 23:57 ` bugzilla-daemon
2017-06-12 23:40 ` bugzilla-daemon
2017-06-14 8:15 ` bugzilla-daemon
2017-06-15 14:19 ` bugzilla-daemon
2017-06-15 15:16 ` bugzilla-daemon
2017-06-15 18:29 ` bugzilla-daemon
2017-06-15 19:33 ` bugzilla-daemon
2017-06-15 19:41 ` bugzilla-daemon
2017-06-15 20:06 ` bugzilla-daemon
2017-06-15 20:24 ` bugzilla-daemon
2017-06-15 20:49 ` bugzilla-daemon
2017-06-15 21:30 ` bugzilla-daemon
2017-06-15 22:05 ` bugzilla-daemon
2017-06-16 22:20 ` bugzilla-daemon
2017-06-19 17:33 ` bugzilla-daemon
2017-06-19 17:42 ` bugzilla-daemon
2017-06-20 10:07 ` bugzilla-daemon
2017-06-20 22:05 ` bugzilla-daemon
2017-06-21 19:38 ` bugzilla-daemon
2017-07-09 20:25 ` bugzilla-daemon
2017-08-31 16:48 ` bugzilla-daemon
2017-09-16 10:55 ` bugzilla-daemon
2017-09-16 10:56 ` bugzilla-daemon
2018-11-07 21:40 ` bugzilla-daemon
2018-11-28 13:28 ` bugzilla-daemon
2019-11-19 9:12 ` 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-93826-502-rOdAFpHaMN@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;
as well as URLs for NNTP newsgroup(s).