<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [CI][SHARDS] igt@i915_suspend@debugfs-reader - dmesg-warn - i915_dsc_fec_support_show" href="https://bugs.freedesktop.org/show_bug.cgi?id=109745#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [CI][SHARDS] igt@i915_suspend@debugfs-reader - dmesg-warn - i915_dsc_fec_support_show" href="https://bugs.freedesktop.org/show_bug.cgi?id=109745">bug 109745</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=109745#c5">comment #5</a>) > commit ee6df5694a9a2e30566ae05e9c145a0f6d5e087f (HEAD -> > drm-intel-next-queued, > drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) > Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> > 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 <a href="show_bug.cgi?id=109745#c4">comment #4</a>) > (In reply to Lakshmi from <a href="show_bug.cgi?id=109745#c3">comment #3</a>) > > 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 ;)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>