From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Steven Newbury <steve@snewbury.org.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
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: Tue, 12 Jul 2016 12:08:17 +0200 [thread overview]
Message-ID: <20160712100817.GV23520@phenom.ffwll.local> (raw)
In-Reply-To: <20160624124206.GB7856@nuc-i3427.alporthouse.com>
On Fri, Jun 24, 2016 at 01:42:06PM +0100, Chris Wilson wrote:
> On Fri, Jun 24, 2016 at 12:48:17PM +0100, Steven Newbury wrote:
> > On Fri, 2016-06-24 at 11:59 +0100, Chris Wilson wrote:
> > > On Thu, Jun 23, 2016 at 02:14:12PM +0100, Steven Newbury wrote:
> > > > On Thu, 2016-06-23 at 15:59 +0300, Jani Nikula wrote:
> > > > > On Thu, 23 Jun 2016, Steven Newbury <steve@snewbury.org.uk>
> > > > > wrote:
> > > > > > 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.
> > > > >
> > > > It must be something else then. Actually, in my case linus/master
> > > > is
> > > > okay. I saw the subject and though it must be the same issue. I'm
> > > > seeing it with drm-intel nightly/next branches. Shall I try to
> > > > bisect
> > > > it? Symptoms are similar, although I would describe it more like
> > > > flashes of a different buffer across parts of the screen.
> > >
> > > Try reverting ee042aa40b66d18d465206845b0752c6a617ba3f instead.
> > > -Chris
> > >
> >
> > Yes, thanks, that "fixed" it. So atomic commits not working properly
> > on IVB?
>
> Not yet it seems. Something seems to be off in the timing, but has so
> far eluded capture.
Fyi we reverted this for now to fix things up:
commit 527b6abe5fd2d24fba69e9564a2d608e1796ca8d
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Fri Jun 24 13:44:03 2016 +0100
Revert "drm/i915: Use atomic commits for legacy page_flips"
Kudos to Chris for handling this in my absence.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-07-12 10:08 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
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 [this message]
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=20160712100817.GV23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=James.Bottomley@HansenPartnership.com \
--cc=chris@chris-wilson.co.uk \
--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