[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915/execlists: Preempt-to-busy

Chris Wilson chris at chris-wilson.co.uk
Thu Jun 20 08:13:27 UTC 2019


Quoting Patchwork (2019-06-20 09:09:33)
> == Series Details ==
> 
> Series: series starting with [1/3] drm/i915/execlists: Preempt-to-busy
> URL   : https://patchwork.freedesktop.org/series/62431/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_6312 -> Patchwork_13359
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_13359 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_13359, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13359/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_13359:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt at i915_module_load@reload:
>     - fi-kbl-r:           [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6312/fi-kbl-r/igt@i915_module_load@reload.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13359/fi-kbl-r/igt@i915_module_load@reload.html
>     - fi-whl-u:           [PASS][3] -> [INCOMPLETE][4]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6312/fi-whl-u/igt@i915_module_load@reload.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13359/fi-whl-u/igt@i915_module_load@reload.html
>     - fi-skl-guc:         [PASS][5] -> [INCOMPLETE][6]
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6312/fi-skl-guc/igt@i915_module_load@reload.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13359/fi-skl-guc/igt@i915_module_load@reload.html

Hmm, new asserts firing. More than likely a bug in the assert or a
latent issue. Still scary.
-Chris


More information about the Intel-gfx mailing list