All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for series starting with [v3,1/2] drm/i915/guc: Reset GuC and retry on firmware load failure
Date: Tue, 29 Mar 2016 13:35:44 +0100	[thread overview]
Message-ID: <56FA76A0.9010206@intel.com> (raw)
In-Reply-To: <20160325083152.28149.8188@emeril.freedesktop.org>

On 25/03/16 08:31, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v3,1/2] drm/i915/guc: Reset GuC and retry on firmware load failure
> URL   : https://patchwork.freedesktop.org/series/4876/
> State : warning
>
> == Summary ==
>
> Series 4876v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/4876/revisions/1/mbox/
>
> Test kms_pipe_crc_basic:
>          Subgroup suspend-read-crc-pipe-c:
>                  pass       -> DMESG-WARN (bsw-nuc-2)

Unrelated, https://bugs.freedesktop.org/show_bug.cgi?id=94350
lockdep splat due to stop_machine() in ggtt pte programming

> Test pm_rpm:
>          Subgroup basic-pci-d3-state:
>                  pass       -> DMESG-WARN (bsw-nuc-2)

Unrelated, https://bugs.freedesktop.org/show_bug.cgi?id=94164
Unclaimed access detected prior to suspending

>          Subgroup basic-rte:
>                  dmesg-warn -> PASS       (byt-nuc) UNSTABLE
>
> bdw-nuci7        total:192  pass:179  dwarn:0   dfail:0   fail:1   skip:12
> bdw-ultra        total:192  pass:170  dwarn:0   dfail:0   fail:1   skip:21
> bsw-nuc-2        total:192  pass:153  dwarn:2   dfail:0   fail:0   skip:37
> byt-nuc          total:192  pass:157  dwarn:0   dfail:0   fail:0   skip:35
> hsw-brixbox      total:192  pass:170  dwarn:0   dfail:0   fail:0   skip:22
> hsw-gt2          total:192  pass:175  dwarn:0   dfail:0   fail:0   skip:17
> ivb-t430s        total:192  pass:167  dwarn:0   dfail:0   fail:0   skip:25
> skl-i7k-2        total:192  pass:169  dwarn:0   dfail:0   fail:0   skip:23
> snb-dellxps      total:192  pass:158  dwarn:0   dfail:0   fail:0   skip:34
> snb-x220t        total:192  pass:158  dwarn:0   dfail:0   fail:1   skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1717/
>
> f5d413cccefa1f93d64c34f357151d42add63a84 drm-intel-nightly: 2016y-03m-24d-14h-34m-29s UTC integration manifest
> cff00fb37026cf1e75d9317e8570938e89197515 drm/i915/guc: always reset GuC before loading firmware
> 6c406232a0289a937e4478901e3edc57c8f9f01a drm/i915/guc: Reset GuC and retry on firmware load failure
>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-03-29 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 18:40 [PATCH v3 1/2] drm/i915/guc: Reset GuC and retry on firmware load failure Dave Gordon
2016-03-24 18:40 ` [PATCH v3 2/2] drm/i915/guc: always reset GuC before loading firmware Dave Gordon
2016-03-29 11:48   ` Daniel Vetter
2016-03-31 11:31     ` Dave Gordon
2016-03-24 18:44 ` [PATCH v3 1/2] drm/i915/guc: Reset GuC and retry on firmware load failure Dave Gordon
2016-03-25  8:31 ` ✗ Fi.CI.BAT: warning for series starting with [v3,1/2] " Patchwork
2016-03-29 12:35   ` Dave Gordon [this message]

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=56FA76A0.9010206@intel.com \
    --to=david.s.gordon@intel.com \
    --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.