From: Jani Nikula <jani.nikula@linux.intel.com>
To: Steven Newbury <steve@snewbury.org.uk>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window
Date: Thu, 23 Jun 2016 15:59:49 +0300 [thread overview]
Message-ID: <87r3bohxh6.fsf@intel.com> (raw)
In-Reply-To: <1466686369.6831.1.camel@snewbury.org.uk>
On Thu, 23 Jun 2016, Steven Newbury <steve@snewbury.org.uk> wrote:
> [ Unknown signature status ]
> On Sun, 2016-06-19 at 14:53 -0700, James Bottomley wrote:
>> On Fri, 2016-06-17 at 16:06 -0700, James Bottomley wrote:
>> > On Fri, 2016-06-17 at 16:34 +0300, Jani Nikula wrote:
>> > > On Fri, 17 Jun 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
>> > > > 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@linux-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.
>> >
>> > OK, so just on the firmware, the system seems less flickery with
>> > the
>> > new 1.4.3 UEFI, so I'm starting to think it is a Skylake errata
>> > issue. The flicker isn't gone for good, but seems to be reboot
>> > dependent (it's there in some boots, but gone on a reboot).
>> >
>> > > This should be easy enough to try before bisecting:
>> > > http://patchwork.freedesktop.org/patch/msgid/1466162081-12042-1-g
>> > > it
>> > > -s
>> > > end-email-mika.kahola@intel.com
>> >
>> > Applying this didn't seem to make a difference: still there on
>> > some
>> > and gone on other reboots.
>>
>> OK, my candidate bad commit is this one:
>>
>> commit a05628195a0d9f3173dd9aa76f482aef692e46ee
>> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Date: Mon Apr 11 10:23:51 2016 +0300
>>
>> drm/i915: Get panel_type from OpRegion panel details
>>
>> After being more careful about waiting to identify flicker, this one
>> seems to be the one the bisect finds. I'm now running v4.7-rc3 with
>> this one reverted and am currently seeing no flicker problems. It
>> is,
>> however, early days because the flicker can hide for long periods, so
>> I
>> 'll wait until Monday evening and a few reboots before declaring
>> victory.
>>
>>
> 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.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-06-23 12:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:59 James Bottomley
2016-05-31 7:51 ` Jani Nikula
2016-05-31 13:33 ` James Bottomley
2016-06-13 10:14 ` Jani Nikula
2016-06-16 21:15 ` James Bottomley
2016-06-16 21:24 ` [Intel-gfx] " Daniel Vetter
2016-06-16 21:29 ` James Bottomley
2016-06-16 22:42 ` James Bottomley
2016-06-17 7:28 ` Daniel Vetter
2016-06-17 13:34 ` Jani Nikula
2016-06-17 16:08 ` James Bottomley
2016-06-17 23:06 ` James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-20 8:03 ` Jani Nikula
2016-06-21 13:53 ` James Bottomley
2016-06-21 15:44 ` Ville Syrjälä
2016-06-21 21:00 ` James Bottomley
2016-06-23 11:25 ` James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-07 16:14 ` Ville Syrjälä
2016-07-07 16:55 ` James Bottomley
2016-07-07 19:19 ` James Bottomley
2016-07-08 10:19 ` Ville Syrjälä
2016-07-08 14:48 ` James Bottomley
2016-07-08 16:56 ` Ville Syrjälä
2016-09-11 14:10 ` James Hogan
2016-09-13 13:59 ` Jani Nikula
2016-06-23 12:52 ` Steven Newbury
2016-06-23 12:59 ` Jani Nikula [this message]
2016-06-23 13:14 ` Steven Newbury
2016-06-24 10:59 ` Chris Wilson
2016-06-24 11:48 ` Steven Newbury
2016-06-24 12:42 ` Chris Wilson
2016-07-12 10:08 ` Daniel Vetter
2016-09-14 9:43 ` Jani Nikula
2016-06-17 8:12 ` Chris Wilson
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=87r3bohxh6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=steve@snewbury.org.uk \
/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
Powered by JetHome