[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1466116932.2257.4.camel@HansenPartnership.com>
Date: Thu, 16 Jun 2016 15:42:12 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Daniel Vetter <daniel@...ll.ch>
Cc: 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, 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.
James
Powered by blists - more mailing lists