All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Cc: "cpaul@redhat.com" <cpaul@redhat.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"stevenhoneyman@gmail.com" <stevenhoneyman@gmail.com>,
	"rclark@redhat.com" <rclark@redhat.com>,
	"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: Fri, 10 Jun 2016 08:44:55 +0200	[thread overview]
Message-ID: <20160610084455.373be60e@kant> (raw)
In-Reply-To: <1465499077.3885.92.camel@intel.com>

On Jun 09 Zanoni, Paulo R wrote:
> 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.
[...]
> > 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.

Perhaps also worth mentioning in the changelog:
Stefan Richter reported kernel freezes (no video artifacts) when fbc is on.
(E3-1245 v3 with HD P4600; openbox and some KDE and LXDE applications,
thread begins at https://lkml.org/lkml/2016/4/26/813)
-- 
Stefan Richter
-======----- -==- -=-=-
http://arcgraph.de/sr/

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Cc: "rclark@redhat.com" <rclark@redhat.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Vetter, Daniel" <daniel.vetter@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"stevenhoneyman@gmail.com" <stevenhoneyman@gmail.com>
Subject: Re: [PATCH] i915/fbc: Disable on HSW by default for now
Date: Fri, 10 Jun 2016 08:44:55 +0200	[thread overview]
Message-ID: <20160610084455.373be60e@kant> (raw)
In-Reply-To: <1465499077.3885.92.camel@intel.com>

On Jun 09 Zanoni, Paulo R wrote:
> 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.
[...]
> > 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.

Perhaps also worth mentioning in the changelog:
Stefan Richter reported kernel freezes (no video artifacts) when fbc is on.
(E3-1245 v3 with HD P4600; openbox and some KDE and LXDE applications,
thread begins at https://lkml.org/lkml/2016/4/26/813)
-- 
Stefan Richter
-======----- -==- -=-=-
http://arcgraph.de/sr/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-06-10  6:53 UTC|newest]

Thread overview: 8+ 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 15:58 ` Lyude
2016-06-09 16:28 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-06-09 19:04 ` [PATCH] " Zanoni, Paulo R
2016-06-10  6:44   ` Stefan Richter [this message]
2016-06-10  6:44     ` Stefan Richter
2016-06-20 21:11     ` Zanoni, Paulo R
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=20160610084455.373be60e@kant \
    --to=stefanr@s5r6.in-berlin.de \
    --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=paulo.r.zanoni@intel.com \
    --cc=rclark@redhat.com \
    --cc=stable@vger.kernel.org \
    --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 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.