From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Steven Honeyman <stevenhoneyman@gmail.com>
Subject: Re: [PATCH] drm/i915/fbc: disable FBC on FIFO underruns
Date: Mon, 13 Jun 2016 13:47:08 +0200 [thread overview]
Message-ID: <20160613134708.7bf68927@kant> (raw)
In-Reply-To: <1465607883-8533-1-git-send-email-paulo.r.zanoni@intel.com>
On Jun 10 Paulo Zanoni wrote:
> Since my test machines don't produce FIFO underrun errors, I tested this by
> creating a debugfs file that just calls intel_fbc_handle_fifo_underrun(). I'd
> appreciate some Tested-by tags, if possible.
Since May 8 I have been using 4.6.0-rc6 patched with
drm-intel-nightly_2016y-05m-06d-14h-29m-58s (from what I understand,
something close to what is now in mainline), and fbc disabled on the
kernel commandline. I have not rebooted since May 8.
For that kernel, i915.enable_fbc=0 is both required and sufficient to
prevent freezes at random points in time (as reported). The
drm-intel-nightly_2016y-05m-06d-14h-29m-58s patch on the other hand has the
effect that there are never any FIFO underruns logged anymore.
If there are no FIFO underruns reported in dmesg, your underrun
detection routine would never hit, would it?
If you nevertheless think it's worth trying, should I test it on top of
4.7-rc3 or on current drm-intel-nightly?
--
Stefan Richter
-======----- -==- -==-=
http://arcgraph.de/sr/
_______________________________________________
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-13 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 1:18 [PATCH] drm/i915/fbc: disable FBC on FIFO underruns Paulo Zanoni
2016-06-11 6:56 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-06-13 11:47 ` Stefan Richter [this message]
2016-06-13 14:33 ` [PATCH] " Zanoni, Paulo R
2016-06-15 12:19 ` Stefan Richter
2016-08-12 23:24 ` Pandiyan, Dhinakaran
2016-08-13 9:05 ` Chris Wilson
2016-08-15 20:49 ` Zanoni, Paulo R
2016-08-15 22:36 ` [PATCH] " Paulo Zanoni
2016-09-02 5:58 ` Pandiyan, Dhinakaran
2016-09-02 14:45 ` Zanoni, Paulo R
2016-09-12 20:02 ` Paulo Zanoni
2016-09-12 20:25 ` Chris Wilson
2016-09-12 21:25 ` Zanoni, Paulo R
2016-09-13 13:38 ` Paulo Zanoni
2016-09-13 13:56 ` Chris Wilson
2016-09-13 17:07 ` Pandiyan, Dhinakaran
2016-08-16 5:57 ` ✗ Ro.CI.BAT: failure for drm/i915/fbc: disable FBC on FIFO underruns (rev2) Patchwork
2016-09-12 20:54 ` ✓ Fi.CI.BAT: success for drm/i915/fbc: disable FBC on FIFO underruns (rev3) Patchwork
2016-09-13 14:19 ` ✗ Fi.CI.BAT: warning for drm/i915/fbc: disable FBC on FIFO underruns (rev4) Patchwork
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=20160613134708.7bf68927@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--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).