[Bug 106373] [CI] igt at drv_module_reload@basic-reload - dmesg-fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0 && Failed to idle engines, declaring wedged!

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue May 22 20:34:23 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106373

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #5 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #4)
> Should be improved by
> 
> commit dd0cf235d81f24c1ba80c4a000bafc9f2dce3840
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Sun May 6 18:13:28 2018 +0100
> 
>     drm/i915: Speed up idle detection by kicking the tasklets
>     
>     We rely on ksoftirqd to run in a timely fashion in order to drain the
>     execlists queue. Quite frequently, it does not. In some cases we may see
>     latencies of over 200ms triggering our idle timeouts and forcing us to
>     declare the driver wedged!
>     
>     Thus we can speed up idle detection by bypassing ksoftirqd in these
>     cases and flush our tasklet to confirm if we are indeed still waiting
>     for the ELSP to drain.
>     
>     v2: Put the execlists.first check back; it is required for handling
>     reset!
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=106373
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
>     Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
>     Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
>     Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20180506171328.30034-1-
> chris at chris-wilson.co.uk

Seems like it did the trick. We used to reproduce the issue every 5-20 runs,
and we have not hit it in 200 runs now. Thanks!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180522/ed05ad51/attachment-0001.html>


More information about the intel-gfx-bugs mailing list