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

### New filters associated

* BLB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_195/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_190/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_191/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_185/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_189/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_194/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_197/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_198/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-blb-e6850/igt@gem_tiled_fence_blits@normal.html

We need to go harderer...

See commit a889580c087a9cf91fddb3832ece284174214183
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Dec 7 13:40:37 2018 +0000

    drm/i915: Flush GPU relocs harder for gen3
    
    Adding an extra MI_STORE_DWORD_IMM to the gpu relocation path for gen3
    was good, but still not good enough. To survive 24+ hours under test we
    needed to perform not one, not two but three extra store-dw. Doing so
    for each GPU relocation was a little unsightly and since we need to
    worry about userspace hitting the same issues, we should apply the dummy
    store-dw into the EMIT_FLUSH.
    
    Fixes: 7dd4f6729f92 ("drm/i915: Async GPU relocation processing")
    References: 7fa28e146994 ("drm/i915: Write GPU relocs harder with gen3")
    Testcase: igt/gem_tiled_fence_blits # blb/pnv
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20181207134037.11848-1-chris@chris-wilson.co.uk

Suggests, if we can't actually find a reason for it, to bump the num_store_dw used for the w/a

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

{- BLB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val -}
{+ BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5794/shard-snb5/igt@gem_tiled_fence_blits@normal.html

Optimistically,

commit 3d325bb211d8cd84c6862c9945185a937395cb44
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sun Mar 24 14:11:16 2019 +0000

    i915: Mark up some forgotten set-domain
    
    It is the user's responsibility to manage their domains. In libdrm, when
    you mmap a pointer, it calls set-domain automatically, but igt requires
    the caller to manage it explicitly, so do so. The vast majority already
    do correct manage the domain as they use the pointer into the mmap, just
    a few have been missed over the years.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Hmm, maybe that means I can relax a889580c087a9c

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

{- BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val -}
{+ BLB SNB ICL: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-icl-y/igt@gem_tiled_fence_blits@normal.html

(In reply to CI Bug Log from comment #5)
> A CI Bug Log filter associated to this bug has been updated:
> 
> {- BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> linear[i] == start_val -}
> {+ BLB SNB ICL: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> linear[i] == start_val +}
> 
> New failures caught by the filter:
> 
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-icl-y/
> igt@gem_tiled_fence_blits@normal.html

This is now seen on fi-icl-y.

(In reply to Lakshmi from comment #6)
> (In reply to CI Bug Log from comment #5)
> > A CI Bug Log filter associated to this bug has been updated:
> > 
> > {- BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> > linear[i] == start_val -}
> > {+ BLB SNB ICL: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> > linear[i] == start_val +}
> > 
> > New failures caught by the filter:
> > 
> >   *
> > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-icl-y/
> > igt@gem_tiled_fence_blits@normal.html
> 
> This is now seen on fi-icl-y.

No. That is not this issue, but a regular icl gpu hang. This bug is truly blb/pnv specific as it a hardware issue.

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

{- BLB SNB ICL: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val -}
{+ BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion: linear[i] == start_val +}


  No new failures caught with the new filter

(In reply to Chris Wilson from comment #7)
> (In reply to Lakshmi from comment #6)
> > (In reply to CI Bug Log from comment #5)
> > > A CI Bug Log filter associated to this bug has been updated:
> > > 
> > > {- BLB SNB: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> > > linear[i] == start_val -}
> > > {+ BLB SNB ICL: igt@gem_tiled_fence_blits@normal - fail - Failed assertion:
> > > linear[i] == start_val +}
> > > 
> > > New failures caught by the filter:
> > > 
> > >   *
> > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-icl-y/
> > > igt@gem_tiled_fence_blits@normal.html
> > 
> > This is now seen on fi-icl-y.
> 
> No. That is not this issue, but a regular icl gpu hang. This bug is truly
> blb/pnv specific as it a hardware issue.

Thanks Chris. I have updated the filters accordingly.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/215.