From: Mika Kahola <mika.kahola@intel.com>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests/kms_pipe_crc_basic: Reset GPU before running subtests
Date: Wed, 07 Jun 2017 11:00:10 +0300 [thread overview]
Message-ID: <1496822410.11332.61.camel@intel.com> (raw)
In-Reply-To: <149675540076.14666.2796761099904765295@mail.alporthouse.com>
On Tue, 2017-06-06 at 14:23 +0100, Chris Wilson wrote:
> Quoting Mika Kahola (2017-06-06 13:33:14)
> >
> > On Tue, 2017-06-06 at 15:27 +0300, Ville Syrjälä wrote:
> > >
> > > On Tue, Jun 06, 2017 at 03:20:46PM +0300, Mika Kahola wrote:
> > > >
> > > >
> > > > It has been noticed by our CI BAT testing that in some 1%-3%
> > > > probability
> > > > kms_pipe_crc_basic subtest read-crc-pipe-x-frame-sequence fails
> > > > when
> > > > comparing gathered CRC frames. However, running
> > > > kms_pipe_crc_basic
> > > > subtests alone i.e. outside BAT I was unable to replicate the
> > > > issue.
> > > >
> > > > The patch proposes a GPU reset before running the subtests.
> > > > This
> > > > way we
> > > > can ensure that GPU register settings are reinitialized if they
> > > > have been
> > > > altered by the tests executed earlier in BAT.
> > > What does GPU reset have to do with display CRCs?
> > It's unclear but when you do it I was unable to replicate this in
> > couple hundred BAT runs. Maybe the error probability just hits
> > below 1%
> > mark with this.
> So trace through what side-effect the reset may have and find the bug
> in
> the kernel.
I'm a bit puzzled with this bug. By running the test alone doesn't
trigger the issue but this occurs only when running fast-feedback.
testlist. Maybe tearing down the previous tests cause some sort of
instability which is then triggered when running this test? Any hints
or pointers where to look at?
> -Chris
--
Mika Kahola - Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-07 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 12:20 [PATCH i-g-t] tests/kms_pipe_crc_basic: Reset GPU before running subtests Mika Kahola
2017-06-06 12:27 ` Ville Syrjälä
2017-06-06 12:33 ` Mika Kahola
2017-06-06 13:23 ` Chris Wilson
2017-06-07 8:00 ` Mika Kahola [this message]
2017-06-07 10:24 ` Chris Wilson
2017-06-07 10:50 ` Mika Kahola
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=1496822410.11332.61.camel@intel.com \
--to=mika.kahola@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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.