public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: ✗ Ro.CI.BAT: failure for series starting with [1/2] Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake."
Date: Fri, 1 Jul 2016 09:52:05 +0100	[thread overview]
Message-ID: <57762F35.5040209@linux.intel.com> (raw)
In-Reply-To: <20160701052043.15185.31533@emeril.freedesktop.org>


On 01/07/16 06:20, Patchwork wrote:
> == Series Details ==
> 
> Series: series starting with [1/2] Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake."
> URL   : https://patchwork.freedesktop.org/series/9332/
> State : failure
> 
> == Summary ==
> 
> Series 9332v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/9332/revisions/1/mbox
> 
> Test drv_hangman:
>          Subgroup error-state-basic:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)

Looks like there is no firmware on the CI machine?

[    8.232519] [drm:intel_guc_init] GuC firmware pending, path i915/skl_guc_ver6_1.bin
[    8.232520] [drm:guc_fw_fetch] before requesting firmware: GuC fw fetch status PENDING
[    8.232889] i915 0000:00:02.0: Direct firmware load for i915/skl_guc_ver6_1.bin failed with error -2
[    8.232928] [drm:guc_fw_fetch] GuC fw fetch status FAIL; err -2, fw           (null), obj           (null)
[    8.232959] [drm:intel_guc_init [i915]] *ERROR* Failed to fetch GuC firmware from i915/skl_guc_ver6_1.bin (error -2)

It used to be there I thought.

Regards,

Tvrtko


> Test drv_module_reload_basic:
>                  dmesg-warn -> DMESG-FAIL (ro-skl3-i5-6260u)
> Test gem_busy:
>          Subgroup basic-blt:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd1:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd2:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-blt:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-bsd:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-bsd1:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-bsd2:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-render:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-parallel-vebox:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-render:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
>          Subgroup basic-vebox:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
> Test gem_cpu_reloc:
>          Subgroup basic:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_cs_tlb:
>          Subgroup basic-default:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_ctx_create:
>          Subgroup basic-files:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_ctx_exec:
>          Subgroup basic:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_ctx_switch:
>          Subgroup basic-default:
>                  pass       -> SKIP       (ro-skl3-i5-6260u)
> Test gem_exec_basic:
>          Subgroup basic-blt:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd1:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-bsd2:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-default:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-render:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-vebox:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-blt:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-bsd:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-bsd1:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-bsd2:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-default:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-render:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup gtt-vebox:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-blt:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-bsd:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-bsd1:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-bsd2:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-default:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-render:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup readonly-vebox:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_exec_create:
>          Subgroup basic:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
> Test gem_exec_flush:
>          Subgroup basic-batch-kernel-default-cmd:
>                  pass       -> FAIL       (ro-byt-n2820)
>          Subgroup basic-batch-kernel-default-uc:
>                  pass       -> FAIL       (ro-skl3-i5-6260u)
>          Subgroup basic-batch-kernel-default-wb:
> WARNING: Long output truncated
> fi-hsw-i7-4770k failed to connect after reboot
> ro-bdw-i7-5557U failed to connect after reboot
> 
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1348/
> 
> b538380 drm-intel-nightly: 2016y-06m-30d-16h-21m-05s UTC integration manifest
> 1531fb6 i915/guc: Add Kabylake GuC Loading
> b3f31a8 Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake."
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-01  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 16:37 [PATCH 1/2] Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake." Rodrigo Vivi
2016-06-30 16:37 ` [PATCH 2/2] i915/guc: Add Kabylake GuC Loading Rodrigo Vivi
2016-07-01 13:06   ` Michel Thierry
2016-07-01  5:20 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake." Patchwork
2016-07-01  8:52   ` Tvrtko Ursulin [this message]
2016-07-01  8:56     ` Chris Wilson
2016-07-01  8:57     ` Tvrtko Ursulin
2016-07-04 10:23   ` Tvrtko Ursulin

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=57762F35.5040209@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox