All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Jakub Bartmiński" <jakub.bartminski@intel.com>,
	Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [v6,1/6] drm/i915/guc: Avoid wasting memory on incorrect GuC pin bias
Date: Fri, 27 Jul 2018 10:51:15 +0100	[thread overview]
Message-ID: <153268507556.7047.16722517505548579967@skylake-alporthouse-com> (raw)
In-Reply-To: <20180727093557.31052.50608@emeril.freedesktop.org>

Quoting Patchwork (2018-07-27 10:35:57)
> == Series Details ==
> 
> Series: series starting with [v6,1/6] drm/i915/guc: Avoid wasting memory on incorrect GuC pin bias
> URL   : https://patchwork.freedesktop.org/series/47328/
> State : failure
> 
> == Summary ==
> 
> = CI Bug Log - changes from CI_DRM_4559 -> Patchwork_9788 =
> 
> == Summary - FAILURE ==
> 
>   Serious unknown changes coming with Patchwork_9788 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_9788, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: https://patchwork.freedesktop.org/api/1.0/series/47328/revisions/1/mbox/
> 
> == Possible new issues ==
> 
>   Here are the unknown changes that may have been introduced in Patchwork_9788:
> 
>   === IGT changes ===
> 
>     ==== Possible regressions ====
> 
>     igt@drv_selftest@live_contexts:
>       {fi-skl-iommu}:     PASS -> DMESG-FAIL

Ok, just guc related explosions. Are you happy that these are the usual
explosions? They do look like the usual fallout to me.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-07-27  9:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  8:53 [PATCH v6 1/6] drm/i915/guc: Avoid wasting memory on incorrect GuC pin bias Jakub Bartmiński
2018-07-27  8:53 ` [PATCH v6 2/6] drm/i915/guc: Do not partition WOPCM if GuC is not used Jakub Bartmiński
2018-07-27 10:20   ` Chris Wilson
2018-07-27 12:04   ` Michal Wajdeczko
2018-07-27  8:53 ` [PATCH v6 3/6] drm/i915/guc: Move the pin bias value from GuC to GGTT Jakub Bartmiński
2018-07-27 10:29   ` Chris Wilson
2018-07-27 12:03     ` Michal Wajdeczko
2018-07-27 12:07       ` Chris Wilson
2018-07-27  8:53 ` [PATCH v6 4/6] drm/i915: Remove unnecessary ggtt_offset_bias from i915_gem_context Jakub Bartmiński
2018-07-27 10:30   ` Chris Wilson
2018-07-27  8:53 ` [PATCH v6 5/6] drm/i915: Add a fault injection point to WOPCM init Jakub Bartmiński
2018-07-27 12:06   ` Michal Wajdeczko
2018-07-27  8:53 ` [PATCH v6 6/6] HAX enable GuC for CI Jakub Bartmiński
2018-07-27  9:16 ` ✗ Fi.CI.SPARSE: warning for series starting with [v6,1/6] drm/i915/guc: Avoid wasting memory on incorrect GuC pin bias Patchwork
2018-07-27  9:35 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-07-27  9:51   ` Chris Wilson [this message]
2018-07-27 10:32     ` Bartminski, Jakub

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=153268507556.7047.16722517505548579967@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jakub.bartminski@intel.com \
    --cc=patchwork@emeril.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.