Bug 111754 - [CI][BAT]igt@i915_selftest@live_workarounds - dmesg-fail - *ERROR* REF workaround lost on before reset!
Summary: [CI][BAT]igt@i915_selftest@live_workarounds - dmesg-fail - *ERROR* REF workar...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-20 07:44 UTC by Lakshmi
Modified: 2019-10-16 10:57 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features: GEM/Other

Attachments

Description Lakshmi 2019-09-20 07:44:12 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6922/fi-tgl-u/igt@i915_selftest@live_workarounds.html

<3> [502.343796] [drm:wa_verify [i915]] *ERROR* REF workaround lost on before reset! (e18c=3020/0, expected 80008000, mask=8000)
<3> [502.344104] i915/intel_workarounds_live_selftests: live_gpu_reset_workarounds failed with error -3
Comment 1 Lakshmi 2019-09-20 07:45:47 UTC 
NOTOURBUG?
Comment 2 Lakshmi 2019-09-20 07:47:52 UTC 
(In reply to Lakshmi from comment #1)
> NOTOURBUG? Same as 108954 ?
Comment 3 CI Bug Log 2019-09-20 07:48:33 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@i915_selftest@live_workarounds - dmesg-fail - *ERROR* REF workaround lost on before reset!
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14448/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14448/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6922/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6922/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14457/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14457/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14458/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14458/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6923/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6923/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14459/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14459/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6924/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6924/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6925/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6925/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14460/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14460/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14461/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14461/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14463/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14463/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14464/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14464/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14466/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14466/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5043/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5045/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5045/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3481/fi-tgl-u/igt@i915_selftest@live_workarounds.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3481/fi-tgl-u2/igt@i915_selftest@live_workarounds.html
Comment 4 Chris Wilson 2019-09-20 11:03:16 UTC 
commit e5de91e68c5ccaf4ef3e5aa265b469e186ebfa65 (HEAD -> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Sep 20 09:12:54 2019 +0100

    Revert "drm/i915/tgl: Implement Wa_1406941453"
    
    Our sanitychecks indicate that while this register is context
    saved/restore, the HW does not preserve this bit within the register --
    it likely doesn't exist, or one of those mythical bits that the
    architects insist does something despite all appearances to the
    contrary.
    
    For reference, SAMPLER_MODE is already in i915_reg.h as
    GEN10_SAMPLER_MODE and is being setup in icl_ctx_workarounds_init() as
    opposed to the chosen location here of rcs_engine_wa_init).
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111754
    Fixes: 7f0cc34b5349 ("drm/i915/tgl: Implement Wa_1406941453")
    Testcase: igt/i915_selftest/live_workarounds
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Lucas De Marchi <lucas.demarchi@intel.com>
    Cc: Stuart Summers <stuart.summers@intel.com>
    Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20190920081254.18389-1-chris@chris-wilson.co.uk
Comment 5 Martin Peres 2019-10-16 10:57:26 UTC 
(In reply to Chris Wilson from comment #4)
> commit e5de91e68c5ccaf4ef3e5aa265b469e186ebfa65 (HEAD ->
> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Fri Sep 20 09:12:54 2019 +0100
> 
>     Revert "drm/i915/tgl: Implement Wa_1406941453"
>     
>     Our sanitychecks indicate that while this register is context
>     saved/restore, the HW does not preserve this bit within the register --
>     it likely doesn't exist, or one of those mythical bits that the
>     architects insist does something despite all appearances to the
>     contrary.
>     
>     For reference, SAMPLER_MODE is already in i915_reg.h as
>     GEN10_SAMPLER_MODE and is being setup in icl_ctx_workarounds_init() as
>     opposed to the chosen location here of rcs_engine_wa_init).
>     
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111754
>     Fixes: 7f0cc34b5349 ("drm/i915/tgl: Implement Wa_1406941453")
>     Testcase: igt/i915_selftest/live_workarounds
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>     Cc: Stuart Summers <stuart.summers@intel.com>
>     Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
>     Cc: Jani Nikula <jani.nikula@linux.intel.com>
>     Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>     Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20190920081254.18389-1-
> chris@chris-wilson.co.uk

Seems to have done the trick, thanks!
Comment 6 CI Bug Log 2019-10-16 10:57:37 UTC 
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.

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.