linux-kernel - Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160617072826.GI23520@phenom.ffwll.local>
Date:	Fri, 17 Jun 2016 09:28:26 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Daniel Vetter <daniel@...ll.ch>,
	Jani Nikula <jani.nikula@...ux.intel.com>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Rodrigo Vivi <rodrigo.vivi@...el.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7
 merge window

On Thu, Jun 16, 2016 at 03:42:12PM -0700, James Bottomley wrote:
> On Thu, 2016-06-16 at 14:29 -0700, James Bottomley wrote:
> > On Thu, 2016-06-16 at 23:24 +0200, Daniel Vetter wrote:
> > > I guess we'll need the bisect on this one to make progress.
> > 
> > Sigh, I was afraid that might be the next step.
> 
> OK, I have a curious data point.  I assumed the problem would be
> somewhere in the drm update, so I started bisecting that at the top. 
>  However, the top most commit:
> 
> commit 1d6da87a3241deb13d073c4125d19ed0e5a0c62c
> Merge: 1f40c49 a39ed68
> Author: Linus Torvalds <torvalds@...ux-foundation.org>
> Date:   Mon May 23 11:48:48 2016 -0700
> 
>     Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
> 
> Isn't actually bad.  There's no flicker here, so whatever caused the
> problem came from some update after this.

There was a fixes pull after this. Might be worth it to restrict to just
the i915 changes, which are just 5b4fd5b1111b1230cd037..157d2c7fad0863222

Looking at those nothing seems to stick out which might explain what's
happening for you.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch