[Bug 104262] [CI] igt at drv_selftest@live_hangcheck - incomplete - Softdog | fail Returncode -11

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Feb 5 16:18:20 UTC 2018


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

--- Comment #14 from Chris Wilson <chris at chris-wilson.co.uk> ---
My bxt stabilised since

commit 8ec21a7c4b52165211b47932c665ab2e9ca488ee
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Feb 5 15:24:29 2018 +0000

    drm/i915/selftests: Use a sacrificial context for hang testing

    Avoid injecting hangs in to the i915->kernel_context in case the GPU
    reset leaves corruption in the context image in its wake (leading to
    continual failures and system hangs after the selftests are ostensibly
    complete). Use a sacrificial kernel_context instead.

    v2: Closing a context is tricky; export a function (for selftests) from
    i915_gem_context.c to get it right.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Michel Thierry <michel.thierry at intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180205152431.12163-2-chris@chris-wilson.co.uk

commit a8b66f2c2f3e03b70a5e72cb5034f8aff669bf34
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Feb 5 15:24:28 2018 +0000

    drm/i915/selftests: Flush old resets between engines

    When injecting rapid resets, we must be careful to at least wait for the
    previous reset to have taken effect and the engine restarted. If we
    perform a second reset before that has happened, we will notice that the
    engine hasn't recovered and declare it lost, wedging the device and
    failing. In practice, since we wait for each hanging batch to start
    before injecting the reset, this too-fast-reset condition can only be
    triggered when moving onto the next engine in the test, so we need only
    wait for the existing reset to complete before switching engines.

    v2: Wrap up the wait inside a safety net to bail out in case of angry hw.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Michel Thierry <michel.thierry at intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180205152431.12163-1-chris@chris-wilson.co.uk

Hopefully the same is true of CI...

-- 
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/20180205/5c41103e/attachment-0001.html>


More information about the intel-gfx-bugs mailing list