Bug 112147

Summary: [CI][BAT][hsw] igt@i915_selftest@live_blt - incoherency
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: HSW i915 features: GEM/Other

Comment 1 Lakshmi 2019-10-28 09:38:23 UTC
(In reply to Lakshmi from comment #0)
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3622/fi-hsw-peppy/
> igt@i915_selftest@live_blt

(i915_selftest:4121) igt_kmod-WARNING: i915/i915_gem_object_blt_live_selftests: igt_copy_blt failed with error -22
(i915_selftest:4121) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling always-on
(i915_selftest:4121) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling display
(i915_selftest:4121) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed with error -22
(i915_selftest:4121) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../lib/igt_kmod.c:548:
(i915_selftest:4121) igt_kmod-CRITICAL: Failed assertion: err == 0
(i915_selftest:4121) igt_kmod-CRITICAL: kselftest "i915 igt__33__live_blt=1 live_selftests=-1 disable_display=1 st_filter=" failed: Invalid argument [22]
(i915_selftest:4121) igt_core-INFO: Stack trace:
(i915_selftest:4121) igt_core-INFO:   #0 ../lib/igt_core.c:1716 __igt_fail_assert()
(i915_selftest:4121) igt_core-INFO:   #1 [igt_kselftest_execute+0x2e5]
(i915_selftest:4121) igt_core-INFO:   #2 ../lib/igt_kmod.c:582 igt_kselftests()
(i915_selftest:4121) igt_core-INFO:   #3 ../tests/i915/i915_selftest.c:43 __real_main29()
(i915_selftest:4121) igt_core-INFO:   #4 ../tests/i915/i915_selftest.c:29 main()
(i915_selftest:4121) igt_core-INFO:   #5 ../csu/libc-start.c:344 __libc_start_main()
(i915_selftest:4121) igt_core-INFO:   #6 [_start+0x2a]
****  END  ****
Subtest live_blt: FAIL (2.396s)
Comment 4 Chris Wilson 2019-10-28 09:43:37 UTC
<6> [503.089053] i915: Performing live selftests with st_random_seed=0xf4b4bced st_timeout=500
<6> [503.089056] i915: Running blt
<6> [503.089080] i915: Running i915_gem_object_blt_live_selftests/igt_fill_blt
<6> [503.781371] i915: Running i915_gem_object_blt_live_selftests/igt_copy_blt
<3> [504.532897] vaddr[0]=733a55b2, expected=ae5feef4
Comment 5 Chris Wilson 2019-10-28 09:44:39 UTC
When 32x MI_STORE_DWORD_INDEX is not enough delay!
Comment 6 CI Bug Log 2019-10-28 10:31:55 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -22 -}
{+ HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -22 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5243/fi-bsw-n3050/igt@i915_selftest@live_blt.html
Comment 7 CI Bug Log 2019-10-28 10:32:47 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -22 -}
{+ BSW HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -\d+ +}


  No new failures caught with the new filter
Comment 8 Chris Wilson 2019-10-28 10:49:02 UTC
(In reply to CI Bug Log from comment #6)
> A CI Bug Log filter associated to this bug has been updated:
> 
> {- HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with
> error -22 -}
> {+ HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with
> error -22 +}
> 
> New failures caught by the filter:
> 
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5243/fi-bsw-n3050/
> igt@i915_selftest@live_blt.html

Please do not put unrelated bugs here. Leave this for incoherency on hsw. Track the aliasing-ppgtt eviction failure elsewhere.
Comment 9 CI Bug Log 2019-10-29 06:46:02 UTC
A CI Bug Log filter associated to this bug has been updated:

{- BSW HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -\d+ -}
{+ HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -\d+ +}


  No new failures caught with the new filter
Comment 10 Chris Wilson 2019-11-12 14:10:38 UTC
Just the normal stab in the dark, 

commit f9228f7658734fe16ef7eec554d187a3d9577be8 (HEAD -> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Nov 11 12:09:57 2019 +0000

    drm/i915/gt: Try an extra flush on the Haswell blitter
    
    On gen7, including Haswell, the MI_FLUSH_DW command is not synchronous
    with the command streamer nor is there an option to make it so. To hide
    this we add a large delay on the CS so that the breadcrumb should always
    be visible before the interrupt. However, that does not seem to be
    enough to ensure the memory is actually coherent with the read of the
    breadcrumb. The breadcrumb update is a post-sync op... Throw in a
    preliminary MI_FLUSH_DW before the breadcrumb update in the hope that
    helps.
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=112147
    Testcase: igt/i915_selftest/live_blt
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20191111120957.17732-1-chris@chris-wilson.co.uk
Comment 11 CI Bug Log 2019-11-13 09:32:44 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -\d+ -}
{+ HSW: igt@i915_selftest@live_blt - dmesg-fail - igt_copy_blt failed with error -22 +}


  No new failures caught with the new filter
Comment 13 Martin Peres 2019-11-29 19:44:29 UTC
-- 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/553.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.