[Intel-gfx] ✗ Fi.CI.BAT: failure for GuC fixes (rev2)

Chris Wilson chris at chris-wilson.co.uk
Thu May 23 20:58:33 UTC 2019


Quoting Michal Wajdeczko (2019-05-23 15:46:58)
> On Wed, 22 May 2019 22:53:11 +0200, Patchwork  
> <patchwork at emeril.freedesktop.org> wrote:
> 
> > == Series Details ==
> >
> > Series: GuC fixes (rev2)
> > URL   : https://patchwork.freedesktop.org/series/60795/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from CI_DRM_6123 -> Patchwork_13075
> > ====================================================
> >
> > Summary
> > -------
> >
> >   **FAILURE**
> >
> >   Serious unknown changes coming with Patchwork_13075 absolutely need to  
> > be
> >   verified manually.
> >  If you think the reported changes have nothing to do with the changes
> >   introduced in Patchwork_13075, 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_13075/
> >
> > Possible new issues
> > -------------------
> >
> >   Here are the unknown changes that may have been introduced in  
> > Patchwork_13075:
> >
> > ### IGT changes ###
> >
> > #### Possible regressions ####
> >
> >   * igt at i915_module_load@reload:
> >     - fi-apl-guc:         [PASS][1] -> [DMESG-WARN][2]
> >    [1]:  
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6123/fi-apl-guc/igt@i915_module_load@reload.html
> >    [2]:  
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13075/fi-apl-guc/igt@i915_module_load@reload.html
> 
> these are doorbells warnings at unload/load when GuC submission is enabled:
> 
> <7> [309.389262] [drm:doorbell_ok [i915]] Doorbell 0 has unexpected state:  
> valid=yes
> <7> [309.389683] [drm:doorbell_ok [i915]] Doorbell 128 has unexpected  
> state: valid=yes
> <4> [309.390061] ------------[ cut here ]------------
> <4> [309.390067] WARN_ON(!guc_verify_doorbells(guc))
> <4> [309.390360] Call Trace:
> <4> [309.390445]  intel_uc_fini+0x46/0x140 [i915]
> <4> [309.390520]  i915_gem_fini+0x70/0x1a0 [i915]
> <4> [309.390585]  i915_driver_unload+0xdd/0x130 [i915]
> <4> [309.390651]  i915_pci_remove+0x19/0x30 [i915]
> 
> ...
> 
> <7> [310.812673] [drm:doorbell_ok [i915]] Doorbell 0 has unexpected state:  
> valid=yes
> <7> [310.813014] [drm:doorbell_ok [i915]] Doorbell 128 has unexpected  
> state: valid=yes
> <4> [310.813290] ------------[ cut here ]------------
> <4> [310.813295] WARN_ON(!guc_verify_doorbells(guc))
> <4> [310.813646] Call Trace:
> <4> [310.813755]  intel_uc_init+0xc8/0x1f0 [i915]
> <4> [310.813856]  i915_gem_init+0x49b/0xa90 [i915]
> <4> [310.813945]  i915_driver_load+0xdb8/0x18b0 [i915]
> 
> and can be fixed by patch [a], but since we are going to disable GuC
> submission soon [b] maybe we don't care to fix that, as it works [c].

Hmm, it's a bit of nuisance as it means CI stops running tests and we
miss the selftests for guc/apl.

I don't think that's a huge issue as we have your gen11 enabling patch
to land in the very near future which as you say makes this a non-issue.
Till then we will just have to upset Martin!

Thanks for the patches, pushed.
-Chris


More information about the Intel-gfx mailing list