Bug 110946

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BDW KBL: igt@gem_sync@basic-store-each - fail - Failed assertion: !"GPU hung"
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/fi-bdw-5557u/igt@gem_sync@basic-store-each.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-kbl-7567u/igt@gem_sync@basic-store-each.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13337/fi-bdw-5557u/igt@gem_sync@basic-store-each.html

Odd. They have the same look of the currently executing ring finished but we did not switch to the second port and didn't get a completion CS. Nothing looked funky in recent commits, but this definitely shouldn't be happening and will cause unpleasant GPU stalls.

Given the indication that engine idling is too soon, this could be more fallout.

*** Bug 110942 has been marked as a duplicate of this bug. ***

[  386.221128] i915: Running i915_gem_context_live_selftests/igt_vm_isolation
[  386.345411] assert_pending_valid:646 GEM_BUG_ON(!intel_context_is_pinned(ce))

A CI Bug Log filter associated to this bug has been updated:

{- BDW KBL: igt@gem_sync@basic-store-each - fail - Failed assertion: !"GPU hung" -}
{+ BDW SKL KBL: igt@gem_sync@basic-store-each - fail - Failed assertion: !"GPU hung" +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6293/shard-skl6/igt@gem_sync@basic-store-each.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6301/fi-skl-iommu/igt@gem_sync@basic-store-each.html

*** Bug 110948 has been marked as a duplicate of this bug. ***

This bug is marked for BDW & KBL.  Hang that was duplicated to this, was happening BXT/SKL/KBL, but not BDW, and another duplicate on ICL => added ICL/SKL/BXT to platforms.

(Bug 110948 has BXT/SKL/KBL error states as attachments.)

commit 09c5ab384f6fb30f834a5777888b4486dd7f015d (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Jun 19 18:01:35 2019 +0100

    drm/i915: Keep rings pinned while the context is active
    
    Remember to keep the rings pinned as well as the context image until the
    GPU is no longer active.
    
    v2: Introduce a ring->pin_count primarily to hide the
    mock_ring that doesn't fit into the normal GGTT vma picture.
    
    v3: Order is important in teardown, ringbuffer submission needs to drop
    the pin count on the engine->kernel_context before it can gleefully free
    its ring.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110946
    Fixes: ce476c80b8bf ("drm/i915: Keep contexts pinned until after the next kernel context switch")
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20190619170135.15281-1-chris@chris-wilson.co.uk

A CI Bug Log filter associated to this bug has been updated:

{- BDW SKL KBL: igt@gem_sync@basic-store-each - fail - Failed assertion: !"GPU hung" -}
{+ BDW SKL KBL ICL: all tests - fail - Failed assertion: !"GPU hung" +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6304/fi-icl-dsi/igt@gem_exec_parallel@basic.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6309/fi-icl-dsi/igt@gem_exec_create@basic.html

A CI Bug Log filter associated to this bug has been updated:

{- BDW SKL KBL ICL: all tests - fail - Failed assertion: !"GPU hung" -}
{+ BDW SKL GLK KBL ICL: all tests - fail - Failed assertion: !"GPU hung" +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6300/shard-glk2/igt@gem_exec_create@forked.html

I'm not seeing anymore the hangs from duplicate bug 110948, so for my part I can verify the fix (except for BXT, due to bug 110848).

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.