Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Extract, polish, and document multicast handling

2022-06-16 Thread Vudum, Lakshminarayana
We have a bug for a similar test timeout on KBL
https://gitlab.freedesktop.org/drm/intel/-/issues/6048
igt@kms_cursor_legacy@pipe-b-torture-move - incomplete - Received signal 
SIGQUIT. Per-test timeout exceeded. Killing the current test with SIGQUIT.

Thanks,
Lakshmi.

-Original Message-
From: Roper, Matthew D  
Sent: Wednesday, June 15, 2022 9:34 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana 
Subject: Re: ✗ Fi.CI.IGT: failure for i915: Extract, polish, and document 
multicast handling

On Thu, Jun 16, 2022 at 03:11:40AM +, Patchwork wrote:
> == Series Details ==
> 
> Series: i915: Extract, polish, and document multicast handling
> URL   : https://patchwork.freedesktop.org/series/105134/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_11758_full -> Patchwork_105134v1_full 
> 
> 
> Summary
> ---
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_105134v1_full absolutely need 
> to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_105134v1_full, please notify your bug team to allow 
> them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (13 -> 12)
> --
> 
>   Missing(1): shard-dg1 
> 
> Possible new issues
> ---
> 
>   Here are the unknown changes that may have been introduced in 
> Patchwork_105134v1_full:
> 
> ### IGT changes ###
> 
>  Possible regressions 
> 
>   * igt@kms_cursor_legacy@pipe-c-torture-bo:
> - shard-skl:  [PASS][1] -> [INCOMPLETE][2]
>[1]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-skl2/igt@kms_cursor_leg...@pipe-c-torture-bo.html
>[2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-skl4
> /igt@kms_cursor_leg...@pipe-c-torture-bo.html

Appears to be a deadlock:

  <3> [923.922958] INFO: task kms_cursor_lega:1361 blocked for more than 61 
seconds.
  <3> [923.923073]   Tainted: G U  W 
5.19.0-rc2-Patchwork_105134v1-ga2644b16f1f0+ #1
  <3> [923.923104] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

This display test wouldn't be affected by the changes to multicast registers in 
this series, so it seems unrelated.

I don't see any matching issue signatures in gitlab, although there are a 
couple incompletes filed against similar tests due to timeout that might have a 
related root cause (e.g., #6216).


Matt

> 
>   
>  Suppressed 
> 
>   The following results come from untrusted machines, tests, or statuses.
>   They do not affect the overall result.
> 
>   * {igt@kms_plane_lowres@tiling-y@pipe-a-edp-1}:
> - {shard-rkl}:NOTRUN -> [SKIP][3] +3 similar issues
>[3]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-rkl-
> 6/igt@kms_plane_lowres@tilin...@pipe-a-edp-1.html
> 
>   
> Known issues
> 
> 
>   Here are the changes found in Patchwork_105134v1_full that come from known 
> issues:
> 
> ### IGT changes ###
> 
>  Issues hit 
> 
>   * igt@gem_ctx_persistence@smoketest:
> - shard-apl:  [PASS][4] -> [FAIL][5] ([i915#5099])
>[4]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl7/igt@gem_ctx_persiste...@smoketest.html
>[5]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl1
> /igt@gem_ctx_persiste...@smoketest.html
> 
>   * igt@gem_eio@unwedge-stress:
> - shard-iclb: [PASS][6] -> [TIMEOUT][7] ([i915#3070])
>[6]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb6/igt@gem_...@unwedge-stress.html
>[7]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb
> 6/igt@gem_...@unwedge-stress.html
> 
>   * igt@gem_exec_balancer@parallel-keep-submit-fence:
> - shard-iclb: [PASS][8] -> [SKIP][9] ([i915#4525]) +2 similar 
> issues
>[8]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb2/igt@gem_exec_balan...@parallel-keep-submit-fence.html
>[9]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb
> 8/igt@gem_exec_balan...@parallel-keep-submit-fence.html
> 
>   * igt@gem_exec_fair@basic-none-solo@rcs0:
> - shard-apl:  [PASS][10] -> [FAIL][11] ([i915#2842])
>[10]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl3/igt@gem_exec_fair@basic-none-s...@rcs0.html
>[11]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl6
> /igt@gem_exec_fair@basic-none-s...@rcs0.html
> 
>   * igt@gem_exec_fair@basic-none@vcs1:
> - shard-iclb: NOTRUN -> [FAIL][12] ([i915#2842])
>[12]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb
> 1/igt@gem_exec_fair@basic-n...@vcs1.html
> 
>   * igt@gem_exec_fair@basic-pace-solo@rcs0:
> - shard-iclb: [PASS][13] -> 

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Extract, polish, and document multicast handling

2022-06-15 Thread Matt Roper
On Thu, Jun 16, 2022 at 03:11:40AM +, Patchwork wrote:
> == Series Details ==
> 
> Series: i915: Extract, polish, and document multicast handling
> URL   : https://patchwork.freedesktop.org/series/105134/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_11758_full -> Patchwork_105134v1_full
> 
> 
> Summary
> ---
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_105134v1_full absolutely need 
> to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_105134v1_full, please notify your bug team to allow 
> them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (13 -> 12)
> --
> 
>   Missing(1): shard-dg1 
> 
> Possible new issues
> ---
> 
>   Here are the unknown changes that may have been introduced in 
> Patchwork_105134v1_full:
> 
> ### IGT changes ###
> 
>  Possible regressions 
> 
>   * igt@kms_cursor_legacy@pipe-c-torture-bo:
> - shard-skl:  [PASS][1] -> [INCOMPLETE][2]
>[1]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-skl2/igt@kms_cursor_leg...@pipe-c-torture-bo.html
>[2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-skl4/igt@kms_cursor_leg...@pipe-c-torture-bo.html

Appears to be a deadlock:

  <3> [923.922958] INFO: task kms_cursor_lega:1361 blocked for more than 61 
seconds.
  <3> [923.923073]   Tainted: G U  W 
5.19.0-rc2-Patchwork_105134v1-ga2644b16f1f0+ #1
  <3> [923.923104] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

This display test wouldn't be affected by the changes to multicast
registers in this series, so it seems unrelated.

I don't see any matching issue signatures in gitlab, although there are
a couple incompletes filed against similar tests due to timeout that might
have a related root cause (e.g., #6216).


Matt

> 
>   
>  Suppressed 
> 
>   The following results come from untrusted machines, tests, or statuses.
>   They do not affect the overall result.
> 
>   * {igt@kms_plane_lowres@tiling-y@pipe-a-edp-1}:
> - {shard-rkl}:NOTRUN -> [SKIP][3] +3 similar issues
>[3]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-rkl-6/igt@kms_plane_lowres@tilin...@pipe-a-edp-1.html
> 
>   
> Known issues
> 
> 
>   Here are the changes found in Patchwork_105134v1_full that come from known 
> issues:
> 
> ### IGT changes ###
> 
>  Issues hit 
> 
>   * igt@gem_ctx_persistence@smoketest:
> - shard-apl:  [PASS][4] -> [FAIL][5] ([i915#5099])
>[4]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl7/igt@gem_ctx_persiste...@smoketest.html
>[5]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl1/igt@gem_ctx_persiste...@smoketest.html
> 
>   * igt@gem_eio@unwedge-stress:
> - shard-iclb: [PASS][6] -> [TIMEOUT][7] ([i915#3070])
>[6]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb6/igt@gem_...@unwedge-stress.html
>[7]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb6/igt@gem_...@unwedge-stress.html
> 
>   * igt@gem_exec_balancer@parallel-keep-submit-fence:
> - shard-iclb: [PASS][8] -> [SKIP][9] ([i915#4525]) +2 similar 
> issues
>[8]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb2/igt@gem_exec_balan...@parallel-keep-submit-fence.html
>[9]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb8/igt@gem_exec_balan...@parallel-keep-submit-fence.html
> 
>   * igt@gem_exec_fair@basic-none-solo@rcs0:
> - shard-apl:  [PASS][10] -> [FAIL][11] ([i915#2842])
>[10]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl3/igt@gem_exec_fair@basic-none-s...@rcs0.html
>[11]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl6/igt@gem_exec_fair@basic-none-s...@rcs0.html
> 
>   * igt@gem_exec_fair@basic-none@vcs1:
> - shard-iclb: NOTRUN -> [FAIL][12] ([i915#2842])
>[12]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb1/igt@gem_exec_fair@basic-n...@vcs1.html
> 
>   * igt@gem_exec_fair@basic-pace-solo@rcs0:
> - shard-iclb: [PASS][13] -> [FAIL][14] ([i915#2842])
>[13]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb8/igt@gem_exec_fair@basic-pace-s...@rcs0.html
>[14]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb5/igt@gem_exec_fair@basic-pace-s...@rcs0.html
> - shard-kbl:  [PASS][15] -> [FAIL][16] ([i915#2842])
>[15]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-kbl1/igt@gem_exec_fair@basic-pace-s...@rcs0.html
>[16]: 
> 

[Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Extract, polish, and document multicast handling

2022-06-15 Thread Patchwork
== Series Details ==

Series: i915: Extract, polish, and document multicast handling
URL   : https://patchwork.freedesktop.org/series/105134/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11758_full -> Patchwork_105134v1_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_105134v1_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_105134v1_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (13 -> 12)
--

  Missing(1): shard-dg1 

Possible new issues
---

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

### IGT changes ###

 Possible regressions 

  * igt@kms_cursor_legacy@pipe-c-torture-bo:
- shard-skl:  [PASS][1] -> [INCOMPLETE][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-skl2/igt@kms_cursor_leg...@pipe-c-torture-bo.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-skl4/igt@kms_cursor_leg...@pipe-c-torture-bo.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * {igt@kms_plane_lowres@tiling-y@pipe-a-edp-1}:
- {shard-rkl}:NOTRUN -> [SKIP][3] +3 similar issues
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-rkl-6/igt@kms_plane_lowres@tilin...@pipe-a-edp-1.html

  
Known issues


  Here are the changes found in Patchwork_105134v1_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@gem_ctx_persistence@smoketest:
- shard-apl:  [PASS][4] -> [FAIL][5] ([i915#5099])
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl7/igt@gem_ctx_persiste...@smoketest.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl1/igt@gem_ctx_persiste...@smoketest.html

  * igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][6] -> [TIMEOUT][7] ([i915#3070])
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb6/igt@gem_...@unwedge-stress.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb6/igt@gem_...@unwedge-stress.html

  * igt@gem_exec_balancer@parallel-keep-submit-fence:
- shard-iclb: [PASS][8] -> [SKIP][9] ([i915#4525]) +2 similar issues
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb2/igt@gem_exec_balan...@parallel-keep-submit-fence.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb8/igt@gem_exec_balan...@parallel-keep-submit-fence.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl:  [PASS][10] -> [FAIL][11] ([i915#2842])
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-apl3/igt@gem_exec_fair@basic-none-s...@rcs0.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl6/igt@gem_exec_fair@basic-none-s...@rcs0.html

  * igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][12] ([i915#2842])
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb1/igt@gem_exec_fair@basic-n...@vcs1.html

  * igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-iclb: [PASS][13] -> [FAIL][14] ([i915#2842])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-iclb8/igt@gem_exec_fair@basic-pace-s...@rcs0.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-iclb5/igt@gem_exec_fair@basic-pace-s...@rcs0.html
- shard-kbl:  [PASS][15] -> [FAIL][16] ([i915#2842])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/shard-kbl1/igt@gem_exec_fair@basic-pace-s...@rcs0.html
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-kbl4/igt@gem_exec_fair@basic-pace-s...@rcs0.html

  * igt@gem_lmem_swapping@parallel-random-engines:
- shard-apl:  NOTRUN -> [SKIP][17] ([fdo#109271] / [i915#4613])
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-apl8/igt@gem_lmem_swapp...@parallel-random-engines.html

  * igt@gem_lmem_swapping@random:
- shard-glk:  NOTRUN -> [SKIP][18] ([fdo#109271] / [i915#4613])
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-glk3/igt@gem_lmem_swapp...@random.html
- shard-kbl:  NOTRUN -> [SKIP][19] ([fdo#109271] / [i915#4613]) +3 
similar issues
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/shard-kbl1/igt@gem_lmem_swapp...@random.html

  * igt@gem_mmap_gtt@fault-concurrent-y:
- shard-snb:  [PASS][20] -> [INCOMPLETE][21] ([i915#5161])
   [20]: