From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Use atomic for dev_priv->mm.bsd_engine_dispatch_index
Date: Thu, 01 Sep 2016 15:32:13 +0300 [thread overview]
Message-ID: <1472733133.8006.0.camel@linux.intel.com> (raw)
In-Reply-To: <20160901122724.GD6358@nuc-i3427.alporthouse.com>
On to, 2016-09-01 at 13:27 +0100, Chris Wilson wrote:
> On Thu, Sep 01, 2016 at 12:20:18PM -0000, Patchwork wrote:
> > Test prime_vgem:
> > Subgroup basic-fence-flip:
> > pass -> FAIL (fi-bdw-5557u)
> Hmm, this is probably some condition I forgot to drain before starting
> the test. What's the actual failure?
(prime_vgem:29095) CRITICAL: Test assertion failure function flip_to_vgem, file prime_vgem.c:651:
(prime_vgem:29095) CRITICAL: Failed assertion: poll(&pfd, 1, 20000) == 1
(prime_vgem:29095) CRITICAL: error: 0 != 1
Subtest basic-fence-flip failed.
**** DEBUG ****
(prime_vgem:29089) ioctl-wrappers-DEBUG: Test requirement passed: has_modifiers
(prime_vgem:29089) ioctl-wrappers-DEBUG: Test requirement passed: has_modifiers
(prime_vgem:29089) DEBUG: Test requirement passed: (crtc_id = set_fb_on_crtc(i915, 0, &bo[0], fb_id[0]))
**** END ****
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-01 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 11:58 [PATCH] drm/i915: Use atomic for dev_priv->mm.bsd_engine_dispatch_index Joonas Lahtinen
2016-09-01 12:08 ` Chris Wilson
2016-09-01 12:20 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-09-01 12:27 ` Chris Wilson
2016-09-01 12:32 ` Joonas Lahtinen [this message]
2016-09-01 12:42 ` Joonas Lahtinen
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=1472733133.8006.0.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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.