From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Daniel Vetter <daniel@ffwll.ch>
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: Mon, 20 Jun 2016 11:03:44 +0300 [thread overview]
Message-ID: <8737o89ti7.fsf@intel.com> (raw)
In-Reply-To: <1466373202.2280.3.camel@HansenPartnership.com>
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.
It might be helpful if you could add drm.debug=14 module parameter, and
provide dmesgs from boot both with and without the above commit (it's
enough to see i915 load). Please also provide
/sys/kernel/debug/dri/0/i915_opregion.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: 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>, "Syrjala\,
Ville" <ville.syrjala@intel.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window
Date: Mon, 20 Jun 2016 11:03:44 +0300 [thread overview]
Message-ID: <8737o89ti7.fsf@intel.com> (raw)
In-Reply-To: <1466373202.2280.3.camel@HansenPartnership.com>
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.
It might be helpful if you could add drm.debug=14 module parameter, and
provide dmesgs from boot both with and without the above commit (it's
enough to see i915 load). Please also provide
/sys/kernel/debug/dri/0/i915_opregion.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-06-20 8:03 UTC|newest]
Thread overview: 72+ 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-05-31 13:33 ` James Bottomley
2016-06-13 10:14 ` Jani Nikula
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:24 ` [Intel-gfx] " Daniel Vetter
2016-06-16 21:29 ` James Bottomley
2016-06-16 21:29 ` James Bottomley
2016-06-16 22:42 ` James Bottomley
2016-06-16 22:42 ` [Intel-gfx] " James Bottomley
2016-06-17 7:28 ` Daniel Vetter
2016-06-17 7:28 ` [Intel-gfx] " Daniel Vetter
2016-06-17 13:34 ` Jani Nikula
2016-06-17 13:34 ` [Intel-gfx] " Jani Nikula
2016-06-17 16:08 ` James Bottomley
2016-06-17 23:06 ` James Bottomley
2016-06-17 23:06 ` [Intel-gfx] " James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-19 21:53 ` [Intel-gfx] " James Bottomley
2016-06-20 8:03 ` Jani Nikula [this message]
2016-06-20 8:03 ` Jani Nikula
2016-06-21 13:53 ` James Bottomley
2016-06-21 13:53 ` [Intel-gfx] " James Bottomley
2016-06-21 15:44 ` Ville Syrjälä
2016-06-21 15:44 ` [Intel-gfx] " Ville Syrjälä
2016-06-21 21:00 ` James Bottomley
2016-06-21 21:00 ` [Intel-gfx] " James Bottomley
2016-06-23 11:25 ` James Bottomley
2016-06-23 11:25 ` James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-02 6:24 ` [Intel-gfx] " Thorsten Leemhuis
2016-07-07 16:14 ` Ville Syrjälä
2016-07-07 16:14 ` Ville Syrjälä
2016-07-07 16:55 ` James Bottomley
2016-07-07 16:55 ` James Bottomley
2016-07-07 19:19 ` James Bottomley
2016-07-07 19:19 ` James Bottomley
2016-07-08 10:19 ` Ville Syrjälä
2016-07-08 10:19 ` Ville Syrjälä
2016-07-08 14:48 ` James Bottomley
2016-07-08 14:48 ` James Bottomley
2016-07-08 16:56 ` Ville Syrjälä
2016-07-08 16:56 ` [Intel-gfx] " 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-09-13 13:59 ` Jani Nikula
2016-06-23 12:52 ` Steven Newbury
2016-06-23 12:59 ` Jani Nikula
2016-06-23 12:59 ` Jani Nikula
2016-06-23 13:14 ` Steven Newbury
2016-06-23 13:14 ` [Intel-gfx] " Steven Newbury
2016-06-24 10:59 ` Chris Wilson
2016-06-24 10:59 ` [Intel-gfx] " Chris Wilson
2016-06-24 11:48 ` Steven Newbury
2016-06-24 11:48 ` Steven Newbury
2016-06-24 12:42 ` Chris Wilson
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
2016-06-17 8:12 ` [Intel-gfx] " 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=8737o89ti7.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=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.