Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Separate display workarounds from clock gating (rev4)

2023-09-11 Thread Jani Nikula
On Fri, 08 Sep 2023, Matt Roper  wrote:
> None of the problems reported here were caused by this series; applied
> to drm-intel-next.  Thanks Lucas for the review.

I'm late to the party, but thanks for doing this. Good stuff.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center


Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Separate display workarounds from clock gating (rev4)

2023-09-08 Thread Matt Roper
On Fri, Sep 08, 2023 at 06:32:46AM +, Patchwork wrote:
> == Series Details ==
> 
> Series: Separate display workarounds from clock gating (rev4)
> URL   : https://patchwork.freedesktop.org/series/123363/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_13612_full -> Patchwork_123363v4_full
> 
> 
> Summary
> ---
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_123363v4_full absolutely need 
> to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_123363v4_full, please notify your bug team 
> (lgci.bug.fil...@intel.com) to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (9 -> 10)
> --
> 
>   Additional (1): shard-tglu0 
> 
> Possible new issues
> ---
> 
>   Here are the unknown changes that may have been introduced in 
> Patchwork_123363v4_full:
> 
> ### IGT changes ###
> 
>  Possible regressions 
> 
>   * igt@gem_ctx_isolation@preservation-s3@ccs2:
> - shard-dg2:  NOTRUN -> [INCOMPLETE][1]
>[1]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-1/igt@gem_ctx_isolation@preservation...@ccs2.html

https://gitlab.freedesktop.org/drm/intel/-/issues/9162

> 
>   * igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
> - shard-apl:  [PASS][2] -> [INCOMPLETE][3]
>[2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-apl2/igt@kms_vbl...@pipe-b-ts-continuation-dpms-suspend.html
>[3]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-apl6/igt@kms_vbl...@pipe-b-ts-continuation-dpms-suspend.html

<3>[  275.640293] i915 :00:02.0: [drm] *ERROR* DPCD read failed, address 
0x5df
<3>[  275.640429] i915 :00:02.0: [drm] *ERROR* Failed to write infoframes
...
<7>[  275.678015] i915 :00:02.0: [drm:intel_read_infoframe [i915]] Failed 
to unpack infoframe type 0x82
<3>[  275.678569] i915 :00:02.0: [drm] *ERROR* [CRTC:88:pipe B] mismatch in 
infoframes.enable (expected 0x, found 0x0008)

after coming out of suspend.  Doesn't appear to be related to this
series; this series didn't make any changes to APL (gen9).

> 
>   * igt@perf@i915-ref-count:
> - shard-apl:  [PASS][4] -> [FAIL][5]
>[4]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-apl4/igt@p...@i915-ref-count.html
>[5]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-apl2/igt@p...@i915-ref-count.html
> - shard-dg2:  NOTRUN -> [FAIL][6]
>[6]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-11/igt@p...@i915-ref-count.html

https://gitlab.freedesktop.org/drm/intel/-/issues/9285

> 
>   
>  Warnings 
> 
>   * igt@gem_exec_schedule@noreorder@ccs0:
> - shard-mtlp: [DMESG-WARN][7] ([i915#9121]) -> [INCOMPLETE][8]
>[7]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-mtlp-4/igt@gem_exec_schedule@noreor...@ccs0.html
>[8]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-mtlp-4/igt@gem_exec_schedule@noreor...@ccs0.html

https://gitlab.freedesktop.org/drm/intel/-/issues/9121
  and
https://gitlab.freedesktop.org/drm/intel/-/issues/8962


None of the problems reported here were caused by this series; applied
to drm-intel-next.  Thanks Lucas for the review.


Matt

> 
>   
> New tests
> -
> 
>   New tests have been introduced between CI_DRM_13612_full and 
> Patchwork_123363v4_full:
> 
> ### New IGT tests (4) ###
> 
>   * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-a-vga-1:
> - Statuses : 1 pass(s)
> - Exec time: [0.0] s
> 
>   * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-b-vga-1:
> - Statuses : 1 pass(s)
> - Exec time: [0.0] s
> 
>   * igt@kms_atomic_transition@plane-all-transition@pipe-a-vga-1:
> - Statuses : 1 pass(s)
> - Exec time: [0.0] s
> 
>   * igt@kms_atomic_transition@plane-all-transition@pipe-b-vga-1:
> - Statuses : 1 pass(s)
> - Exec time: [0.0] s
> 
>   
> 
> Known issues
> 
> 
>   Here are the changes found in Patchwork_123363v4_full that come from known 
> issues:
> 
> ### IGT changes ###
> 
>  Issues hit 
> 
>   * igt@drm_fdinfo@busy-idle@bcs0:
> - shard-dg2:  NOTRUN -> [SKIP][9] ([i915#8414]) +20 other tests 
> skip
>[9]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-7/igt@drm_fdinfo@busy-i...@bcs0.html
> 
>   * igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
> - shard-rkl:  [PASS][10] -> [FAIL][11] ([i915#7742])
>[10]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-rkl-7/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
>[11]: 
> 

[Intel-gfx] ✗ Fi.CI.IGT: failure for Separate display workarounds from clock gating (rev4)

2023-09-08 Thread Patchwork
== Series Details ==

Series: Separate display workarounds from clock gating (rev4)
URL   : https://patchwork.freedesktop.org/series/123363/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_13612_full -> Patchwork_123363v4_full


Summary
---

  **FAILURE**

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

  

Participating hosts (9 -> 10)
--

  Additional (1): shard-tglu0 

Possible new issues
---

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

### IGT changes ###

 Possible regressions 

  * igt@gem_ctx_isolation@preservation-s3@ccs2:
- shard-dg2:  NOTRUN -> [INCOMPLETE][1]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-1/igt@gem_ctx_isolation@preservation...@ccs2.html

  * igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-apl:  [PASS][2] -> [INCOMPLETE][3]
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-apl2/igt@kms_vbl...@pipe-b-ts-continuation-dpms-suspend.html
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-apl6/igt@kms_vbl...@pipe-b-ts-continuation-dpms-suspend.html

  * igt@perf@i915-ref-count:
- shard-apl:  [PASS][4] -> [FAIL][5]
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-apl4/igt@p...@i915-ref-count.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-apl2/igt@p...@i915-ref-count.html
- shard-dg2:  NOTRUN -> [FAIL][6]
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-11/igt@p...@i915-ref-count.html

  
 Warnings 

  * igt@gem_exec_schedule@noreorder@ccs0:
- shard-mtlp: [DMESG-WARN][7] ([i915#9121]) -> [INCOMPLETE][8]
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-mtlp-4/igt@gem_exec_schedule@noreor...@ccs0.html
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-mtlp-4/igt@gem_exec_schedule@noreor...@ccs0.html

  
New tests
-

  New tests have been introduced between CI_DRM_13612_full and 
Patchwork_123363v4_full:

### New IGT tests (4) ###

  * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-a-vga-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-b-vga-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_atomic_transition@plane-all-transition@pipe-a-vga-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_atomic_transition@plane-all-transition@pipe-b-vga-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  

Known issues


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

### IGT changes ###

 Issues hit 

  * igt@drm_fdinfo@busy-idle@bcs0:
- shard-dg2:  NOTRUN -> [SKIP][9] ([i915#8414]) +20 other tests skip
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-7/igt@drm_fdinfo@busy-i...@bcs0.html

  * igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- shard-rkl:  [PASS][10] -> [FAIL][11] ([i915#7742])
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13612/shard-rkl-7/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-rkl-4/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html

  * igt@feature_discovery@chamelium:
- shard-dg2:  NOTRUN -> [SKIP][12] ([i915#4854])
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-7/igt@feature_discov...@chamelium.html

  * igt@gem_basic@multigpu-create-close:
- shard-mtlp: NOTRUN -> [SKIP][13] ([i915#7697])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-mtlp-5/igt@gem_ba...@multigpu-create-close.html

  * igt@gem_busy@semaphore:
- shard-dg2:  NOTRUN -> [SKIP][14] ([i915#3936])
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-11/igt@gem_b...@semaphore.html

  * igt@gem_ccs@suspend-resume@xmajor-compressed-compfmt0-lmem0-lmem0:
- shard-dg2:  NOTRUN -> [INCOMPLETE][15] ([i915#7297])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123363v4/shard-dg2-10/igt@gem_ccs@suspend-res...@xmajor-compressed-compfmt0-lmem0-lmem0.html

  * igt@gem_close_race@multigpu-basic-process:
- shard-dg2:  NOTRUN -> [SKIP][16] ([i915#7697])
   [16]: