https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4476/fi-cfl-guc/igt@drv_selftest@live_guc.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4476/fi-kbl-guc/igt@drv_selftest@live_guc.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4477/fi-cfl-guc/igt@drv_selftest@live_guc.html [drm:intel_guc_send_mmio [i915]] *ERROR* MMIO: GuC action 0x10 failed with error -5 0xf000f000
The spam is a regression from commit 13295bd887d07a9d904401808f41a8d35946d8c2 Author: Michal Wajdeczko <michal.wajdeczko@intel.com> Date: Mon May 28 17:16:18 2018 +0000 drm/i915/guc: Don't read SOFT_SCRATCH(15) on MMIO error SOFT_SCRATCH(15) is used by GuC for sending MMIO GuC events to host and those events are now handled by intel_guc_to_host_event_handler_mmio(). We should not try to read it on MMIO action error as 1) we may be using different set of registers for GuC MMIO communication, and 2) GuC may use CTB mechanism for sending events to host. While here, upgrade error message to DRM_ERROR. Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com> Cc: Michel Thierry <michel.thierry@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20180528171618.10436-1-michal.wajdeczko@intel.com
Raising the priority to high as it spams every run.
*** Bug 107186 has been marked as a duplicate of this bug. ***
*** Bug 107837 has been marked as a duplicate of this bug. ***
CI disabled guc submission, so no longer being triggered.
Chris, this issue has occurred again https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5007/fi-apl-guc/igt@drv_selftest@live_guc.html
The test has been removed so it won't happen again. commit e346a991f42ca2a397166ac73445832966aa8968 Author: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Date: Wed Oct 17 17:46:05 2018 -0700 drm/i915/guc: drop negative doorbell alloc selftest
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.