[Bug 103479] igt@[gem_flink_basic at bad-open | igt at drv_module_reload@basic-reload] *ERROR* Timeout waiting for engines to idle

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
This is likely a side-effect of changing the wait loops in:

commit 5427f207852d5b905e251a5a728c8604d3594d58
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Oct 23 22:32:34 2017 +0100

    drm/i915: Bump wait-times for the final CS interrupt before parking

    In the idle worker we drop the prolonged GT wakeref used to cover such
    essentials as interrupt delivery. (When a CS interrupt arrives, we also
    assert that the GT is awake.) However, it turns out that 10ms is not
    long enough to be assured that the last CS interrupt has been delivered,
    so bump that to 200ms, and move the entirety of that wait to before we
    take the struct_mutex to avoid blocking. As this is now a potentially
    long wait, restore the earlier behaviour of bailing out early when a new
    request arrives.

Afaict, the warning should be genuine, we really should have waited 200ms since
the last request for the confirmation CS interrupt.

Anyway, the plan for this is that we are going to move the warning into
intel_engines_park() so we can do a detailed state_warn for each of the engines
to identify what we think is still active.

-- 
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/20171027/4a249a1b/attachment.html>