[Bug 107711] [BAT] igt at gem_eio@(reset-stress|wait-10ms|wait-1us) - fail - Failed assertion: elapsed < 250e6

[bugzilla-daemon at freedesktop.org]

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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
These are conflating errors. The missed breadcrumb should be fixed by

commit a4a717010f4e8cacaa3f0cae8a22f25c39ae1d41
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Aug 8 11:51:00 2018 +0100

    drm/i915: Unmask user interrupts writes into HWSP on snb/ivb/vlv/hsw

    An oddity occurs on Sandybridge, Ivybridge and Haswell (and presumably
    Valleyview) in that for the period following the GPU restart after a
    reset, there are no GT interrupts received. From Ville's notes, bit 0 in
    the HWSTAM corresponds to the render interrupt, and if we unmask it we
    do see immediate resumption of GT interrupt delivery (via the master irq
    handler) after the reset.

    v2: Limit the w/a to the render interrupt from rcs

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107500
    Fixes: c5498089463b ("drm/i915: Mask everything in ring HWSTAM on gen6+ in
ringbuffer mode")
    References: d420a50c21ef ("drm/i915: Clean up the HWSTAM mess")
    Testcase: igt/gem_eio/reset-stress
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Ville Syrjälä <ville.syrjala at linux.intel.com>
    Acked-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180808105101.913-2-chris@chris-wilson.co.uk

then

commit d6fee0dee09317d5e83e9b855316cb779dd679cf
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Aug 14 11:40:56 2018 +0100

    drm/i915: Kick waiters on resetting legacy rings

    This reapplies commit 39f3be162c46 ("drm/i915: Kick waiters on resetting
    legacy rings") after the improved gem_eio was run across all machines we
    found that gen3 and early gen4 still lost the immediate interrupt
    following reset, and the HWSTAM w/a applied to gen6+ is inadequate.

    Unlike the later gen, on gen3/4 the principle (and only tests to fail so
    far) are the wait vs reset test cases, whereas the reset stress case
    works fine (which was the predominantly failing case for gen6+). That is
    enough to suggest the underlying issue is sufficiently different to
    support the difference in HWSTAM efficacy.

    Testcase: igt/gem_eio/wait-10ms
    References: 39f3be162c46 ("drm/i915: Kick waiters on resetting legacy
rings")
    References: a69ab52b0358 ("drm/i915: Remove extra waiter kick on legacy
resets")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Matthew Auld <matthew.auld 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/20180814104056.27001-1-chris@chris-wilson.co.uk

However, there are later results reported here that do not have an explanation
(nothing reported at all in dmesg for the missing interval).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list 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/20180828/31463252/attachment-0001.html>