Re: ✗ Fi.CI.BAT: failure for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)

[John Harrison <john.c.harrison@xxxxxxxxx>]

Title: Project List - Patchwork

    On 10/12/2023 06:45, Patchwork wrote:

Patch Details

Series:	drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)
URL:	https://patchwork.freedesktop.org/series/125002/
State:	failure
Details:	https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_125002v2/index.html

CI Bug Log - changes from CI_DRM_13746 -> Patchwork_125002v2

Summary

FAILURE

Serious unknown changes coming with Patchwork_125002v2 absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_125002v2, please notify your bug team (lgci.bug.filing@xxxxxxxxx) to allow them
to document this new failure mode, which will reduce false positives in CI.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_125002v2/index.html

Participating hosts (38 -> 38)

Additional (1): fi-bsw-n3050
Missing (1): fi-snb-2520m

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_125002v2:

IGT changes

Possible regressions

• igt@i915_selftest@live@gt_mocs:

  • bat-mtlp-8: PASS -> DMESG-WARN +1 other test dmesg-warn

• igt@i915_selftest@live@guc:

  • bat-mtlp-6: PASS -> DMESG-WARN +3 other tests dmesg-warn

  • bat-mtlp-8: NOTRUN -> DMESG-WARN +1 other test dmesg-warn
    

    These failure all appear to be reset related. However, they are full
    GT reset not individual engine resets. So not sure they can be
    explained by the worker thread vs interrupt handler processing issue
    of the gem_exec_capture failures.
    
    I would definitely recommend running these locally when you have the
    next version of the patch set ready.
    
    John.