From: Chris Wilson <chris@chris-wilson.co.uk>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Daniel Vetter <daniel@ffwll.ch>,
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: Fri, 24 Jun 2016 11:59:30 +0100 [thread overview]
Message-ID: <20160624105930.GA27113@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1466687652.6831.8.camel@snewbury.org.uk>
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
--
Chris Wilson, Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: 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: Bad flicker on skylake HQD due to code in the 4.7 merge window
Date: Fri, 24 Jun 2016 11:59:30 +0100 [thread overview]
Message-ID: <20160624105930.GA27113@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1466687652.6831.8.camel@snewbury.org.uk>
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
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-24 10:59 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 ` [Intel-gfx] " Daniel Vetter
2016-06-16 21:24 ` Daniel Vetter
2016-06-16 21:29 ` [Intel-gfx] " James Bottomley
2016-06-16 21:29 ` James Bottomley
2016-06-16 22:42 ` James Bottomley
2016-06-16 22:42 ` James Bottomley
2016-06-17 7:28 ` [Intel-gfx] " Daniel Vetter
2016-06-17 7:28 ` Daniel Vetter
2016-06-17 13:34 ` [Intel-gfx] " Jani Nikula
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-17 23:06 ` James Bottomley
2016-06-19 21:53 ` [Intel-gfx] " James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-20 8:03 ` [Intel-gfx] " Jani Nikula
2016-06-20 8:03 ` Jani Nikula
2016-06-21 13:53 ` James Bottomley
2016-06-21 13:53 ` James Bottomley
2016-06-21 15:44 ` [Intel-gfx] " Ville Syrjälä
2016-06-21 15:44 ` Ville Syrjälä
2016-06-21 21:00 ` [Intel-gfx] " James Bottomley
2016-06-21 21:00 ` James Bottomley
2016-06-23 11:25 ` [Intel-gfx] " James Bottomley
2016-06-23 11:25 ` James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-07 16:14 ` [Intel-gfx] " 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 ` 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 ` Steven Newbury
2016-06-24 10:59 ` Chris Wilson [this message]
2016-06-24 10:59 ` Chris Wilson
2016-06-24 11:48 ` [Intel-gfx] " 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 ` 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=20160624105930.GA27113@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=daniel@ffwll.ch \
--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 \
--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 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.