From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH igt] tests/kms_frontbuffer_tracking: increase FBC wait timeout to 5s
Date: Wed, 21 Mar 2018 11:17:25 -0700 [thread overview]
Message-ID: <1521656245.3150.2.camel@intel.com> (raw)
In-Reply-To: <152159436823.2146.5478909311393493798@mail.alporthouse.com>
Em Qua, 2018-03-21 às 01:06 +0000, Chris Wilson escreveu:
> Quoting Paulo Zanoni (2018-03-21 00:29:45)
> > From: "Lofstedt, Marta" <marta.lofstedt@intel.com>
> >
> > This is a partial revert of:
> > 64590c7b768dc8d8dd962f812d5ff5a39e7e8b54
> > ("kms_frontbuffer_tracking:
> > reduce the FBC wait timeout to 2s")
> >
> > The subtests: igt@kms_frontbuffer_tracking@fbc-*draw* have
> > non-consistent results, pending between fail and pass. The fails
> > are
> > always due to "FBC disabled". With this increase in timeout the
> > flip-flop behavior is no longer reproducible.
>
> We haven't seen this behaviour for a few months, afaict. Currently we
> have FBC perma-disabled due to bad mode, underruns and whatnot, and
> flip flops from CRC mismatches. But no FBC timeouts waiting for
> enable.
Then why is it being reported as highest-priority-needs-to-be-fixed-
immediately to me? The goal of the patch would be to try to reduce the
flip-flopping caused by the low timeout so we can better split this
type of problem from the others that may be happening.
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-03-21 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 0:29 [igt-dev] [PATCH igt] tests/kms_frontbuffer_tracking: increase FBC wait timeout to 5s Paulo Zanoni
2018-03-21 1:06 ` Chris Wilson
2018-03-21 8:02 ` Lofstedt, Marta
2018-03-21 18:17 ` Paulo Zanoni [this message]
2018-03-21 9:15 ` [igt-dev] ✗ Fi.CI.BAT: warning for " 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=1521656245.3150.2.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
/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.