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]

Date:	Fri, 24 Jun 2016 13:42:06 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Steven Newbury <steve@...wbury.org.uk>
Cc:	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	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 Fri, Jun 24, 2016 at 12:48:17PM +0100, Steven Newbury wrote:
> On Fri, 2016-06-24 at 11:59 +0100, Chris Wilson wrote:
> > On Thu, Jun 23, 2016 at 02:14:12PM +0100, Steven Newbury wrote:
> > > On Thu, 2016-06-23 at 15:59 +0300, Jani Nikula wrote:
> > > > On Thu, 23 Jun 2016, Steven Newbury <steve@...wbury.org.uk>
> > > > wrote:
> > > > > I'm seeing this on my IvyBridge.  I'll try reverting the commit
> > > > > here
> > > > > too, to see if it's the same issue.
> > > > 
> > > > IvyBridge doesn't have low vswing for eDP. If reverting helps,
> > > > it's a
> > > > different failure mode.
> > > > 
> > > It must be something else then.  Actually, in my case linus/master
> > > is
> > > okay.  I saw the subject and though it must be the same issue.  I'm
> > > seeing it with drm-intel nightly/next branches.  Shall I try to
> > > bisect
> > > it?  Symptoms are similar, although I would describe it more like
> > > flashes of a different buffer across parts of the screen.
> > 
> > Try reverting ee042aa40b66d18d465206845b0752c6a617ba3f instead.
> > -Chris
> > 
> 
> Yes, thanks, that "fixed" it.  So atomic commits not working properly
> on IVB?

Not yet it seems. Something seems to be off in the timing, but has so
far eluded capture.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre