https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@i915_suspend@debugfs-reader.html <4> [1601.870376] WARNING: CPU: 3 PID: 8445 at drivers/gpu/drm/drm_modeset_lock.c:228 drm_modeset_drop_locks+0x35/0x40 <4> [1601.870427] RIP: 0010:drm_modeset_drop_locks+0x35/0x40 <4> [1601.870505] i915_dsc_fec_support_show+0x91/0x190 [i915] <4> [1601.870616] WARNING: CPU: 3 PID: 8445 at drivers/gpu/drm/drm_modeset_lock.c:228 drm_modeset_drop_locks+0x35/0x40
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@i915_suspend@debugfs-reader - dmesg-warn - i915_dsc_fec_support_show - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@i915_suspend@debugfs-reader.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@runner@aborted - fail - Previous test: i915_suspend (debugfs-reader) - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@runner@aborted.html
Vanshidhar, Any updates here?
(In reply to Lakshmi from comment #3) > Vanshidhar, Any updates here? Hello Lakshmi, this issue has not reproduced in > 30 days. I would suggest closing it.
commit ee6df5694a9a2e30566ae05e9c145a0f6d5e087f (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Mar 29 16:51:52 2019 +0000 drm/i915: Always backoff after a drm_modeset_lock() deadlock If drm_modeset_lock() reports a deadlock it sets the ctx->contexted field and insists that the caller calls drm_modeset_backoff() or else it generates a WARN on cleanup.
(In reply to Chris Wilson from comment #5) > commit ee6df5694a9a2e30566ae05e9c145a0f6d5e087f (HEAD -> > drm-intel-next-queued, > drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) > Author: Chris Wilson <chris@chris-wilson.co.uk> > Date: Fri Mar 29 16:51:52 2019 +0000 > > drm/i915: Always backoff after a drm_modeset_lock() deadlock > > If drm_modeset_lock() reports a deadlock it sets the ctx->contexted > field and insists that the caller calls drm_modeset_backoff() or else it > generates a WARN on cleanup. Thanks! (In reply to Vanshidhar Konda from comment #4) > (In reply to Lakshmi from comment #3) > > Vanshidhar, Any updates here? > > Hello Lakshmi, this issue has not reproduced in > 30 days. I would suggest > closing it. This is why looking at the reproduction rate is bad ;) The issue is real, just improbable. Next time, please investigate the logs more thoroughly and understand what the failure means ;)
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.