From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
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: Fri, 08 Jul 2016 07:48:29 -0700 [thread overview]
Message-ID: <1467989309.2245.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160708101934.GQ4329@intel.com>
On Fri, 2016-07-08 at 13:19 +0300, Ville Syrjälä wrote:
> On Thu, Jul 07, 2016 at 12:19:36PM -0700, James Bottomley wrote:
> > On Thu, 2016-07-07 at 09:55 -0700, James Bottomley wrote:
> > > On Thu, 2016-07-07 at 19:14 +0300, Ville Syrjälä wrote:
> > > > On Tue, Jun 21, 2016 at 06:44:34PM +0300, Ville Syrjälä wrote:
> > > > > On Tue, Jun 21, 2016 at 09:53:15AM -0400, James Bottomley
> > > > > wrote:
> > > > > > On Mon, 2016-06-20 at 11:03 +0300, Jani Nikula wrote:
> > > > > > > Cc: Ville
> > > > > > >
> > > > > > > On Mon, 20 Jun 2016, James Bottomley <
> > > > > > > James.Bottomley@HansenPartnership.com> wrote:
> > > > > > > > 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.
> > > > > > >
> > > > > > > If that turns out to be the bad commit, it doesn't really
> > > > > > > surprise me, and that in itself is depressing.
> > > > > >
> > > > > > As far as I can tell, after running for a day with this
> > > > > > reverted,
> > > > > > this is the problem. The flicker hasn't appeared with it
> > > > > > reverted. It's pretty noticeable with this commit
> > > > > > included.
> > > > >
> > > > > Hmm. The only difference I can see is low vs. normal vswing.
> > > > > Panel
> > > > > 0 has low, panel 2 has normal. So either the VBT or opregion
> > > > > is
> > > > > telling utter lies, or there's some other bug in our low
> > > > > vswing
> > > > > support.
> > > >
> > > > I did a quick once over of out DDI vswing stuff and didn't find
> > > > anything too serious. There were some buglets in the iboost
> > > > handling,
> > > > but I'm not very hopeful that fixing those would help with your
> > > > machine.
> > > >
> > > > Here's a branch anyway in case you want to give it a go:
> > > > git://github.com/vsyrjala/linux.git ddi_iboost_fixes
> > > >
> > > > Actually, I think the only patch in there that might make a
> > > > difference is 15d887855180 ("drm/i915: Fix iboost setting for
> > > > DDI
> > > > with 4 lanes on SKL")
> > >
> > > Running with it now (the entire branch). So far it looks OK, but
> > > I'll give it a couple of days to see if anything manifests before
> > > declaring victory.
> >
> > Bad news, I'm afraid: after a couple of hours of run time, there is
> > now
> > noticeable flicker on the display, so although the iboost fixes may
> > have lessened it, it's still present.
>
> Oh well, I suspected as much. Which BIOS version did you have
> exactly?
As mentioned upthread, now 1.4.3 since skylake microcode was
potentially implicated in the problem:
http://mid.gmane.org/1466179729.2271.33.camel@HansenPartnership.com
> If I'm reading the Dell website correctly there's a new one (1.4.4)
> released on Jun 30, which is after you reported the issue. Might be
> I'm reading the wrong thing though. Can you double check this?
New bios doesn't change the microcode:
[ 2.390172] microcode: CPU0 sig=0x406e3, pf=0x80, revision=0x8a
And the flicker is still present.
James
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-08 14:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:59 Bad flicker on skylake HQD due to code in the 4.7 merge window 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 ` Daniel Vetter
2016-06-16 21:29 ` [Intel-gfx] " 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 ` [Intel-gfx] " James Bottomley
2016-06-17 23:06 ` James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-20 8:03 ` [Intel-gfx] " 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 ` [Intel-gfx] " James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-07 16:14 ` [Intel-gfx] " 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 [this message]
2016-07-08 16:56 ` Ville Syrjälä
2016-07-12 12:00 ` [PATCH] drm/i915: Ignore panel type from OpRegion on SKL ville.syrjala
2016-07-13 12:04 ` Daniel Vetter
2016-07-13 13:09 ` Ville Syrjälä
2016-07-13 13:33 ` James Bottomley
2016-07-13 13:36 ` Ville Syrjälä
2016-07-14 13:12 ` Ville Syrjälä
2016-07-12 13:12 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-07-14 13:02 ` Ville Syrjälä
2016-09-11 14:10 ` [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window James Hogan
2016-09-13 13:59 ` Jani Nikula
2016-06-23 12:52 ` Steven Newbury
2016-06-23 12:59 ` Jani Nikula
2016-06-23 13:14 ` Steven Newbury
2016-06-24 10:59 ` Chris Wilson
2016-06-24 11:48 ` [Intel-gfx] " 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=1467989309.2245.2.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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).