<3> [371.037146] [drm:i915_gem_init_hw [i915]] *ERROR* Enabling uc failed (-110)
<3> [371.037194] [drm:i915_reset [i915]] *ERROR* Failed to initialise HW following reset (-110)
<3> [371.057507] i915/intel_hangcheck_live_selftests: igt_reset_queue failed with error -5
Setting the bug to HIGH because it is hit in BAT (which warrants HIGHEST), but the GUC is disabled by default (which warrants MEDIUM).
Possibly due to an intermittent Gen9 guc reload issue that can requires retry workaround and that will be tested. Otherwise, further investigation will be deferred until after upcoming update to guc version.
Last seen this issue CI_DRM_5446 (2 months, 1 week / 1348 runs ago)
Robert/Jon, Any updates here?
Code has been implemented for the retry mechanism and is to be tested against cases of spurious load failure.
commit 52b832606038c5b3cb1070e7653e4115b7942606 (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Robert M. Fosha <email@example.com>
Date: Fri Mar 29 16:17:46 2019 -0700
drm/i915/guc: Retry GuC load for all load failures
Currently we only retry to load GuC firmware if the load fails due to
timeout. On Gen9 GuC loading may fail for different reasons, not just
hang/timeout. Direction from the GuC team is to retry for all cases of
GuC load failure on Gen9, not just for timeout.
Signed-off-by: Robert M. Fosha <firstname.lastname@example.org>
Cc: Daniele Ceraolo Spurio <email@example.com>
Cc: Michal Wajdeczko <firstname.lastname@example.org>
Reviewed-by: Chris Wilson <email@example.com>
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
The CI Bug Log issue associated to this bug has been archived.
New failures matching the above filters will not be associated to this bug anymore.