From: Daniel Vetter <daniel@ffwll.ch>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.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, 16 Jun 2016 23:24:31 +0200 [thread overview]
Message-ID: <CAKMK7uGCn6rWGArnOah8bWojkWRdTPr8LeSdJb8iBojh8bHs-w@mail.gmail.com> (raw)
In-Reply-To: <1466111747.2311.1.camel@HansenPartnership.com>
On Thu, Jun 16, 2016 at 11:15 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Mon, 2016-06-13 at 13:14 +0300, Jani Nikula wrote:
>> On Tue, 31 May 2016, James Bottomley <
>> James.Bottomley@HansenPartnership.com> wrote:
>> > On Tue, 2016-05-31 at 10:51 +0300, Jani Nikula wrote:
>> > > On Mon, 30 May 2016, James Bottomley <
>> > > James.Bottomley@HansenPartnership.com> wrote:
>> > > > I've tested a pristine 4.6.0 system, so it's definitely
>> > > > something
>> > > > that
>> > > > went in during the merge window. The flicker isn't continuous,
>> > > > it's
>> > > > periodic, with an interval of something like 2-5 seconds. It
>> > > > looks
>> > > > like an old analogue TV going out of sync and then resyncing.
>> > > > I've
>> > > > attached the dmesg and X.org log below just in case they can
>> > > > help.
>> > > > I
>> > > > might be able to bisect this next week, but, unfortunately,
>> > > > this is
>> > > > my
>> > > > current laptop and I'm travelling this week.
>> > >
>> > > Please try i915.enable_psr=0 module parameter.
>> >
>> > Makes no discernable difference. Current parameter settings are:
>>
>> Sorry for the silence. Would you mind trying out drm-intel-nightly
>> branch of [1]?
>>
>> BR,
>> Jani.
>>
>> [1] http://cgit.freedesktop.org/drm-intel
>
> No, flicker is still there (and in fact seems worse) with the tree with
> this commit at the top:
>
> commit 3eb202ecc3668583f9ff4338211dbab47d755d1c
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Thu Jun 16 14:38:54 2016 +0200
>
> drm-intel-nightly: 2016y-06m-16d-12h-38m-37s UTC integration
> manifest
Strange indeed, I hoped the improved watermark code in -nightly would
help. I assume nothing in dmesg about underruns or something similar?
I guess we'll need the bisect on this one to make progress.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2016-06-16 21:24 UTC|newest]
Thread overview: 36+ 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 [this message]
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 ` 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
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=CAKMK7uGCn6rWGArnOah8bWojkWRdTPr8LeSdJb8iBojh8bHs-w@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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).