<7> [348.691642] [drm:intel_uc_fw_upload [i915]] GuC fw load i915/bxt_guc_ver9_29.bin
<7> [348.691710] [drm:intel_uc_fw_upload [i915]] GuC fw load PENDING
<7> [348.792143] [drm:guc_fw_xfer [i915]] GuC status 0x400000a0
<3> [348.792214] [drm:guc_fw_xfer [i915]] *ERROR* GuC firmware signature verification failed
<7> [348.792330] [drm:intel_uc_fw_upload [i915]] GuC fw load FAIL
<4> [348.792335] [drm] GuC: Failed to load firmware i915/bxt_guc_ver9_29.bin (error -8)
<3> [348.792343] i915 0000:00:02.0: GuC initialization failed -8
<3> [348.792434] [drm:i915_gem_init_hw [i915]] *ERROR* Enabling uc failed (-8)
<3> [348.792522] [drm:i915_reset [i915]] *ERROR* Failed to initialise HW following reset (-8)
This is an RSA signature failure after resume from S3. Interestingly we have already successfully recovered twice before from gem_exec_suspend tests for S3 and S4 before hitting this issue on the kms suspend test. Can't tell from the log if this test is consistently failing or this is an intermittent issue.
This might be related to the WaEnableGuCBootHashCheckNotSet issue and that is being checked.
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 drmtip_193 (1 month, 2 weeks / 976 runs ago).
Dropping the priority to high.