Re: ✗ Ro.CI.BAT: failure for series starting with [1/2] Revert "drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake."

Chris Wilson
2016-07-01T08:56:54Z

On Fri, Jul 01, 2016 at 09:52:05AM +0100, Tvrtko Ursulin wrote:
>
> 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.

Also, we still appear to be emitting an *ERROR* for what is handled, and
considering the volatility of the firmware, the norm.

Does the guc not yet emit the instructions on where to find the
firmware [01.org]?
-Chris

--
Chris Wilson, Intel Open Source Technology Centre