https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6997/fi-glk-dsi/igt@i915_selftest@live_gtt.html <3> [367.908132] [drm:wa_verify [i915]] *ERROR* engine workaround lost on load! (20e0=1/0, expected 40004000, mask=4000) <3> [382.183280] i915/i915_gem_gtt_live_selftests: igt_cs_tlb failed with error -5
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * GLK: igt@i915_selftest@live_gtt - dmesg-fail- *ERROR* engine workaround lost on load! - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6997/fi-glk-dsi/igt@i915_selftest@live_gtt.html
We suspect the display (dmc?) causes the register fubar, and it seems no coincidence that it causes the TLB bug. This is a grave error.
Note the engine workload is bug 110788.
Setting severity to major (grave error!), priority medium for now as it happened once in 6 days (in BAT though)
A CI Bug Log filter associated to this bug has been updated: {- GLK: igt@i915_selftest@live_gtt - dmesg-fail- *ERROR* engine workaround lost on load! -} {+ SKL GLK: igt@i915_selftest@live_gtt - dmesg-fail- *ERROR* engine workaround lost on load! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7199/fi-skl-6600u/igt@i915_selftest@live_gtt.html
Note the engine workaround lost again before the TLB snafu.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/481.
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.