All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT:  failure for drm/i915: CCS prep stuff
Date: Wed, 8 Mar 2017 14:11:21 +0000	[thread overview]
Message-ID: <20170308141121.GP25284@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20170308140805.GH31595@intel.com>

On Wed, Mar 08, 2017 at 04:08:05PM +0200, Ville Syrjälä wrote:
> On Wed, Mar 08, 2017 at 01:52:09PM -0000, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: drm/i915: CCS prep stuff
> > URL   : https://patchwork.freedesktop.org/series/20851/
> > State : failure
> > 
> > == Summary ==
> > 
> > Series 20851v1 drm/i915: CCS prep stuff
> > https://patchwork.freedesktop.org/api/1.0/series/20851/revisions/1/mbox/
> > 
> > Test gem_exec_flush:
> >         Subgroup basic-uc-set-default:
> >                 pass       -> INCOMPLETE (fi-skl-6770hq)
> 
> Going to chuck this into the same bucket as
> https://bugs.freedesktop.org/show_bug.cgi?id=100112
> 
> I also see a few in the skl-600hq long term results. The common
> pattern seems to be skl+gem_exec_flush (the specific subtest
> varies between runs).

Afaict, it is not a i915.ko bug. It seems to be that the exit_handler in
the test running is not killing off its children, and that causes piglit
to wait forever. We have a workaround for that that should be hitting CI
the next time it refreshes igt.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-08 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 19:42 [PATCH 0/5] drm/i915: CCS prep stuff ville.syrjala
2017-03-07 19:42 ` [PATCH 1/5] drm/i915: Plumb drm_framebuffer into more places ville.syrjala
2017-03-07 19:42 ` [PATCH 2/5] drm/i915: Move nv12 chroma plane handling into intel_surf_alignment() ville.syrjala
2017-03-07 19:42 ` [PATCH 3/5] drm/i915: Avoid div-by-zero when computing aux_stride w/o an aux plane ville.syrjala
2017-03-07 19:42 ` [PATCH 4/5] drm/i915: Pass the correct plane index to _intel_compute_tile_offset() ville.syrjala
2017-03-07 19:42 ` [PATCH v2 5/5] drm/i915: Use DRM_DEBUG_KMS() for framebuffer failure debug messages ville.syrjala
2017-03-07 20:22 ` ✗ Fi.CI.BAT: warning for drm/i915: CCS prep stuff Patchwork
2017-03-07 20:43   ` Ville Syrjälä
2017-03-08 13:52 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-03-08 14:08   ` Ville Syrjälä
2017-03-08 14:11     ` Chris Wilson [this message]
2017-03-08 14:51 ` [PATCH 0/5] " Ville Syrjälä

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=20170308141121.GP25284@nuc-i3427.alporthouse.com \
    --to=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.