https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3500/shard-kbl7/igt@drv_suspend@fence-restore-tiled2untiled.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3501/shard-kbl1/igt@drv_suspend@fence-restore-tiled2untiled.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3502/shard-kbl5/igt@drv_suspend@fence-restore-tiled2untiled.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3503/shard-kbl2/igt@drv_suspend@fence-restore-tiled2untiled.html 4 time in a row incomplete on differet kbl machines! This deserves a special bug. Unfortunately not much to go in in run.log nor dmesg. And since pstore is currently broken there is not much to go on here.
Possibly: commit 16c8619a7c53fe05526c31d4758be0eeabd16364 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Dec 19 22:09:16 2017 +0000 drm/i915: Avoid context dereference inside execlists_submission_tasklet A lesson that has to be relearnt over and over again is that the request does not keep a reference to the context and so we cannot freely dereference the context from inside the execlists_submission_tasklet. In particular, we try to do so in the new GEM_TRACE() so convert those over to the port->context_id we keep for GEM debugging. This means the tracing now depends on DRM_I915_GEM_DEBUG. Fixes: bccd3b831185 ("drm/i915: Use trace_printk to provide a death rattle for GEM") References: https://bugs.freedesktop.org/show_bug.cgi?id=104066 References: https://bugs.freedesktop.org/show_bug.cgi?id=104162 References: https://bugs.freedesktop.org/show_bug.cgi?id=104242 References: https://bugs.freedesktop.org/show_bug.cgi?id=104310 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Michel Thierry <michel.thierry@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20171219220916.30882-1-chris@chris-wilson.co.uk
Last seen: CI_DRM_3531: 2017-12-16 / 179 runs ago
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.