igt@* - incomplete [correlates with multiple engines] - the red death

Submitted by LAKSHMINARAYANA VUDUM @l4kshmi

Assigned to Mika Kuoppala

Link to original bug (#111880)

Description

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6984/fi-tgl-u/igt@gem_sync@basic-many-each.html
<6> [130.627934] Console: switching to colour dummy device 80x25
<6> [130.627984] [IGT] gem_sync: executing
<5> [130.634550] Setting dangerous option reset - tainting kernel
<6> [130.637426] [IGT] gem_sync: starting subtest basic-many-each

Blocking

• Bug 111646
• Bug 111746
• Bug 111801
• Bug 111831
• Bug 111832
• Bug 111833
• Bug 111850
• Bug 111852
• Bug 111855
• Bug 111866
• Bug 111867
• Bug 111884
• Bug 111886
• Bug 111887
• Bug 111899
• Bug 111998
• Bug 112396
• Bug 111835

added CI feature: GEM platform: TGL priority::highest severity::critical + 1 deleted label

CI Bug Log said:

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

New filters associated

* fi-tgl-u: igt@gem_sync@* - incomplete
(No new failures associated)

Francesco Balestrieri @baleboy said:

This is the biggest cause of TGL instabilities at the moment, setting priority accordingly.

Chris Wilson @ickle said:

This also correlates with rps (currently disabled). Re-enabling rps leads to https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14604/index.html? [notable early deaths in tgl]

Francesco Balestrieri @baleboy closed a related bug:

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

Francesco Balestrieri @baleboy closed a related bug:

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

CI Bug Log said:

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

New filters associated

* shard-tglb* fi-tgl-u2: igt@gem_sync@* - incomplete - system hang
- https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5282/shard-tglb9/igt@gem_sync@basic-all.html
- https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7349/shard-tglb9/igt@gem_sync@basic-all.html
- https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15149/shard-tglb9/igt@gem_sync@basic-store-all.html

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

New filters associated

• TGL: igt@gem_exec_@ - incomplete - system hang
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3537/shard-tglb1/igt@gem_exec_parallel@vecs0-contexts.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5263/shard-tglb8/igt@gem_exec_parallel@vecs0-contexts.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5298/shard-tglb3/igt@gem_exec_parallel@vecs0-contexts.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3787/shard-tglb4/igt@gem_exec_parallel@vecs0-contexts.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15513/shard-tglb5/igt@gem_exec_suspend@basic-s0.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7451/shard-tglb6/igt@gem_exec_schedule@independent-vebox.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7455/shard-tglb4/igt@gem_exec_parallel@vecs0-contexts.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7455/shard-tglb4/igt@gem_exec_parallel@vecs0-fds.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7456/shard-tglb6/igt@gem_exec_suspend@basic-s0.html

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

{- TGL: igt@gem_exec_@ - incomplete - system hang -} {+ TGL: igt@gem_exec_@ - incomplete - system hang +}

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7471/shard-tglb6/igt@gem_exec_reloc@basic-active.html

changed title from {-[CI] [fi-tgl-u]: igt@gem_sync@ - incomplete [correlates with multiple engines]-}* to {+igt@ - incomplete [correlates with multiple engines] - the red death+}*

marked #469 (closed) as a duplicate of this issue

marked #463 (closed) as a duplicate of this issue

marked #461 (closed) as a duplicate of this issue

marked #457 (closed) as a duplicate of this issue

marked #455 (closed) as a duplicate of this issue

marked #416 (closed) as a duplicate of this issue

marked #751 (closed) as a duplicate of this issue

marked #647 (closed) as a duplicate of this issue

marked #539 (closed) as a duplicate of this issue

marked #500 (closed) as a duplicate of this issue