Bug 111998 - [CI][SHARDS] igt@* - system hang - incomplete - No relevant logs related to the failure
Summary: [CI][SHARDS] igt@* - system hang - incomplete - No relevant logs related to t...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on: 111880
Blocks:
  Show dependency treegraph
 
Reported: 2019-10-14 11:43 UTC by Lakshmi
Modified: 2019-11-01 08:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 CI Bug Log 2019-10-14 11:44:15 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@* - system hang - incomplete - No relevant logs related to the failure
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5221/shard-tglb6/igt@gem_mmap_gtt@hang.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-tglb4/igt@gem_ctx_switch@vcs1.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7069/shard-tglb6/igt@gem_eio@in-flight-1us.html
Comment 2 Francesco Balestrieri 2019-10-17 15:22:27 UTC
This looks like another way to track Bug 111880. Any reason for not closing this as duplicate?
Comment 3 CI Bug Log 2019-10-18 08:24:17 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7099/fi-tgl-u2/igt@gem_wait@basic-busy-all.html
Comment 4 CI Bug Log 2019-10-18 20:20:37 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7130/shard-tglb6/igt@gem_eio@wait-10ms.html
Comment 5 CI Bug Log 2019-10-25 14:23:58 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/re-tgl-u/igt@kms_fbcon_fbt@psr.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/re-tgl-u/igt@panfrost_submit@pan-submit.html
Comment 6 CI Bug Log 2019-10-29 08:31:55 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5245/shard-tglb3/igt@gem_ctx_shared@q-out-order-blt.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5247/shard-tglb6/igt@gem_pipe_control_store_loop@reused-buffer.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7197/shard-tglb6/igt@gem_pipe_control_store_loop@reused-buffer.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7199/shard-tglb6/igt@gem_exec_schedule@smoketest-bsd2.html
Comment 7 CI Bug Log 2019-10-30 07:50:03 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7203/shard-tglb6/igt@gem_ctx_switch@all-heavy.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7205/shard-tglb7/igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-wc.html
Comment 8 CI Bug Log 2019-10-30 11:27:17 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7212/shard-tglb8/igt@gem_sync@basic-many-each.html
Comment 9 CI Bug Log 2019-10-31 08:09:19 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7219/shard-tglb6/igt@gem_exec_schedule@smoketest-vebox.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7221/shard-tglb8/igt@gem_sync@basic-each.html
Comment 10 CI Bug Log 2019-10-31 16:38:33 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@* - system hang - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7224/shard-tglb6/igt@gem_exec_blt@dumb-buf.html
Comment 11 Francesco Balestrieri 2019-11-01 05:54:05 UTC
This looks like a meta bug for all TGL incompletes without logs. We need to keep following it, but the actual fixes will be in more specific bugs causing incompletes.
Comment 12 CI Bug Log 2019-11-01 08:46:08 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@* - system hang - incomplete - No relevant logs related to the failure -}
{+ TGL: igt@*  - incomplete - No relevant logs related to the failure +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7225/shard-tglb5/igt@perf_pmu@most-busy-check-all-rcs0.html


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.