Bug 109228 - [CI][BAT] igt@i915_selftest@live_hangcheck - dmesg-fail - MMIO: GuC action 0x501 failed with error -110 0x501
Summary: [CI][BAT] igt@i915_selftest@live_hangcheck - dmesg-fail - MMIO: GuC action 0x...
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Jon Ewins
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Reported: 2019-01-04 15:22 UTC by Martin Peres
Modified: 2019-03-08 17:08 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: firmware/guc


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-01-04 15:22:24 UTC

<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
Comment 2 Jon Ewins 2019-02-15 23:32:17 UTC
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.
Comment 3 Martin Peres 2019-03-08 17:08:39 UTC
Used to happen every 11.5 runs, and now not seen since CI_DRM_5425 (~300 runs ago). Closing!
Comment 4 CI Bug Log 2019-03-08 17:08:56 UTC
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.