https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5333/fi-apl-guc/igt@i915_selftest@live_hangcheck.html <3> [531.827798] i915/intel_hangcheck_live_selftests: igt_reset_idle_engine failed with error -5 <7> [531.828175] [drm:intel_power_well_enable [i915]] enabling power well 2 <7> [531.828289] [drm:intel_power_well_enable [i915]] enabling dpio-common-a <7> [531.830147] [drm:intel_power_well_enable [i915]] enabling dpio-common-bc <3> [531.858613] [drm:intel_guc_send_mmio [i915]] *ERROR* MMIO: GuC action 0x501 failed with error -110 0x501 <7> [531.859653] [drm:intel_uc_suspend [i915]] Failed to suspend GuC, err=-110 <4> [531.970743] i915: probe of 0000:00:02.0 failed with error -5
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * GUC: igt@i915_selftest@live_hangcheck - dmesg-fail - MMIO: GuC action 0x501 failed with error -110 0x501 - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_3422/fi-apl-guc/igt@i915_selftest@live_hangcheck.html - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_3423/fi-apl-guc/igt@i915_selftest@live_hangcheck.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5333/fi-apl-guc/igt@i915_selftest@live_hangcheck.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11134/fi-apl-guc/igt@i915_selftest@live_hangcheck.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11147/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
Issue reported on BXT part with boot parameter i915.enable_guc=3, which means submission via guc enabled. Further investigation will be deferred until after upcoming update to guc version and only if issue seen with i915.enable_guc=2 (no submission via GuC) which is support model for Gen9.
Used to happen every 11.5 runs, and now not seen since CI_DRM_5425 (~300 runs ago). Closing!
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.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.