[Bug 101600] [BAT][PNV,BLB] i915_reset_device timed out, cancelling all in-flight rendering. provokes a dmesg-warn
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Mar 8 15:53:16 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=101600
--- Comment #11 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #10)
> dmesg spam be silenced (by avoiding the mutex deadlock in this and only this
> scenario):
>
> commit 8d52e447807b350b98ffb4e64bc2fcc1f181c5be
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date: Sat Jun 23 11:39:51 2018 +0100
>
> drm/i915: Defer modeset cleanup to a secondary task
>
> If we avoid cleaning up the old state immediately in
> intel_atomic_commit_tail() and defer it to a second task, we can avoid
> taking heavily contended locks when the caller is ready to procede.
> Subsequent modesets will wait for the cleanup operation (either directly
> via the ordered modeset wq or indirectly through the atomic helperr)
> which keeps the number of inflight cleanup tasks in check.
>
> As an example, during reset an immediate modeset is performed to disable
> the displays before the HW is reset, which must avoid struct_mutex to
> avoid recursion. Moving the cleanup to a separate task, defers acquiring
> the struct_mutex to after the GPU is running again, allowing it to
> complete. Even in a few patches time (optimist!) when we no longer
> require struct_mutex to unpin the framebuffers, it will still be good
> practice to minimise the number of contention points along reset. The
> mutex dependency still exists (as one modeset flushes the other), but in
> the short term it resolves the deadlock for simple reset cases.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101600
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> Link:
> https://patchwork.freedesktop.org/patch/msgid/20180623103951.23889-1-
> chris at chris-wilson.co.uk
> Acked-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
> Acked-by: Daniel Vetter <daniel.vetter at ffwll.ch>
Thanks! Closing!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190308/926ce3a2/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list