From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "cpaul@redhat.com" <cpaul@redhat.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"stefanr@s5r6.in-berlin.de" <stefanr@s5r6.in-berlin.de>,
"stevenhoneyman@gmail.com" <stevenhoneyman@gmail.com>,
"rclark@redhat.com" <rclark@redhat.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [PATCH] i915/fbc: Disable on HSW by default for now
Date: Thu, 9 Jun 2016 19:04:40 +0000 [thread overview]
Message-ID: <1465499077.3885.92.camel@intel.com> (raw)
In-Reply-To: <1465487895-7401-1-git-send-email-cpaul@redhat.com>
Em Qui, 2016-06-09 às 11:58 -0400, Lyude escreveu:
> From https://bugs.freedesktop.org/show_bug.cgi?id=96461 :
>
> This was kind of a difficult bug to track down. If you're using a
> Haswell system running GNOME and you have fbc completely enabled and
> working, playing videos can result in video artifacts. Steps to
> reproduce:
>
> - Run GNOME
> - Ensure FBC is enabled and active
> - Download a movie, I used the ogg version of Big Buck Bunny for this
> - Run `gst-launch-1.0 filesrc location='some_movie.ogg' ! decodebin !
> glimagesink` in a terminal
> - Watch for about over a minute, you'll see small horizontal lines go
> down the screen.
If you "dmesg | grep -i underrun", do you see anything (even if it
doesn't happen during the moments of corruption)?
Does the problem still happen if you apply these patches?
- https://patchwork.freedesktop.org/patch/79567/
- https://patchwork.freedesktop.org/patch/80857/
- https://patchwork.freedesktop.org/patch/92634/
>
> For the time being, disable FBC for Haswell by default.
In case we want to improve the commit message:
We also got reports from Steven Honeyman on openbox+roxterm, and from
Stefan Richter.
Anyway, there's a regression that needs to be fixed, so:
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
We can always try again later.
>
> Signed-off-by: Lyude <cpaul@redhat.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/intel_fbc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_fbc.c
> b/drivers/gpu/drm/i915/intel_fbc.c
> index 0f0492f..28f4407 100644
> --- a/drivers/gpu/drm/i915/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/intel_fbc.c
> @@ -823,8 +823,7 @@ static bool intel_fbc_can_choose(struct
> intel_crtc *crtc)
> {
> struct drm_i915_private *dev_priv = crtc->base.dev-
> >dev_private;
> struct intel_fbc *fbc = &dev_priv->fbc;
> - bool enable_by_default = IS_HASWELL(dev_priv) ||
> - IS_BROADWELL(dev_priv);
> + bool enable_by_default = IS_BROADWELL(dev_priv);
>
> if (intel_vgpu_active(dev_priv->dev)) {
> fbc->no_fbc_reason = "VGPU is active";
next prev parent reply other threads:[~2016-06-09 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 15:58 [PATCH] i915/fbc: Disable on HSW by default for now Lyude
2016-06-09 19:04 ` Zanoni, Paulo R [this message]
2016-06-10 6:44 ` Stefan Richter
2016-06-20 21:11 ` Zanoni, Paulo R
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=1465499077.3885.92.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=airlied@linux.ie \
--cc=cpaul@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=rclark@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stevenhoneyman@gmail.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).