Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/edid/firmware: stop using a throwaway platform device
Issue si related to https://gitlab.freedesktop.org/drm/intel/-/issues/6794.
Re-reported.
Lakshmi.
-Original Message-
From: Nikula, Jani
Sent: Monday, November 14, 2022 5:33 PM
To: Patchwork ; Vudum, Lakshminarayana
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/edid/firmware: stop using a throwaway
platform device
On Mon, 14 Nov 2022, Patchwork wrote:
> == Series Details ==
>
> Series: drm/edid/firmware: stop using a throwaway platform device
> URL : https://patchwork.freedesktop.org/series/110859/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12376 -> Patchwork_110859v1
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_110859v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_110859v1, please notify your bug team 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_110859v1/index.html
>
> Participating hosts (37 -> 37)
> --
>
> Additional (2): bat-kbl-2 fi-bsw-nick
> Missing(2): fi-bdw-samus bat-dg1-5
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_110859v1:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@live@mman:
> - fi-rkl-guc: [PASS][1] -> [TIMEOUT][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12376/fi-rkl-guc/igt@i915_selftest@l...@mman.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-rkl-guc
> /igt@i915_selftest@l...@mman.html
Completely unrelated.
BR,
Jani.
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_110859v1 that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_lmem_swapping@basic:
> - fi-apl-guc: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#4613]) +3
> similar issues
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-apl-guc
> /igt@gem_lmem_swapp...@basic.html
>
> * igt@gem_lmem_swapping@parallel-random-engines:
> - fi-bsw-nick:NOTRUN -> [SKIP][4] ([fdo#109271]) +38 similar
> issues
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-bsw-nic
> k/igt@gem_lmem_swapp...@parallel-random-engines.html
>
> * igt@i915_pm_rpm@basic-pci-d3-state:
> - bat-adlp-4: [PASS][5] -> [DMESG-WARN][6] ([i915#7077])
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12376/bat-adlp-4/igt@i915_pm_...@basic-pci-d3-state.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/bat-adlp-4
> /igt@i915_pm_...@basic-pci-d3-state.html
>
> * igt@kms_chamelium@common-hpd-after-suspend:
> - fi-rkl-11600: NOTRUN -> [SKIP][7] ([fdo#111827])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-rkl-116
> 00/igt@kms_chamel...@common-hpd-after-suspend.html
>
> * igt@kms_chamelium@hdmi-crc-fast:
> - fi-apl-guc: NOTRUN -> [SKIP][8] ([fdo#109271] / [fdo#111827])
> +8 similar issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-apl-guc
> /igt@kms_chamel...@hdmi-crc-fast.html
>
> * igt@kms_chamelium@hdmi-hpd-fast:
> - fi-bsw-nick:NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827])
> +8 similar issues
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-bsw-nic
> k/igt@kms_chamel...@hdmi-hpd-fast.html
>
> * igt@kms_force_connector_basic@force-connector-state:
> - fi-apl-guc: NOTRUN -> [SKIP][10] ([fdo#109271]) +11 similar
> issues
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-apl-guc
> /igt@kms_force_connector_ba...@force-connector-state.html
>
>
> Possible fixes
>
> * igt@gem_render_tiled_blits@basic:
> - fi-apl-guc: [INCOMPLETE][11] ([i915#7056]) -> [PASS][12]
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12376/fi-apl-guc/igt@gem_render_tiled_bl...@basic.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110859v1/fi-apl-guc
> /igt@gem_render_tiled_bl...@basic.html
>
> * igt@i915_selftest@live@migrate:
> - {bat-adlp-6}: [INCOMPLETE][13] ([i915#7348]) -> [PASS][14]
>[13]:
> https://intel-gfx-ci.0
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915/ttm: fix uaf with lmem_userfault_list handling
Known issue. Re-reported. -Original Message- From: Auld, Matthew Sent: Tuesday, November 8, 2022 1:40 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915/ttm: fix uaf with lmem_userfault_list handling On 08/11/2022 00:09, Patchwork wrote: > *Patch Details* > *Series:* series starting with [1/2] drm/i915/ttm: fix uaf with > lmem_userfault_list handling > *URL:*https://patchwork.freedesktop.org/series/110613/ > <https://patchwork.freedesktop.org/series/110613/> > *State:* failure > *Details:* > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110613v1/index.html > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110613v1/index.htm > l> > > > CI Bug Log - changes from CI_DRM_12351_full -> > Patchwork_110613v1_full > > > Summary > > *FAILURE* > > Serious unknown changes coming with Patchwork_110613v1_full absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_110613v1_full, please notify your bug team to > allow them to document this new failure mode, which will reduce false > positives in CI. > > > Participating hosts (9 -> 9) > > No changes in participating hosts > > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_110613v1_full: > > > IGT changes > > > Possible regressions > > * > > igt@kms_plane_alpha_blend@constant-alpha-min@pipe-a-dp-1: > > o shard-apl: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-apl8/igt@kms_plane_alpha_blend@constant-alpha-...@pipe-a-dp-1.html> > -> FAIL > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110613v1/shard-apl2/igt@kms_plane_alpha_blend@constant-alpha-...@pipe-a-dp-1.html> > * > > igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend: > > o shard-skl: NOTRUN -> INCOMPLETE > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110613v1/shard-skl > 4/igt@kms_vbl...@pipe-a-ts-continuation-dpms-suspend.html> Unrelated. These platforms don't have lmem. > > > Known issues > > Here are the changes found in Patchwork_110613v1_full that come from > known issues: > > > CI changes > > > Issues hit > > * boot: > o shard-glk: (PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk7/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk3/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk3/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk9/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk5/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk9/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk9/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk8/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk8/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk5/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk5/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk6/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk6/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk6/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk7/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk8/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk7/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk1/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk1/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk1/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk2/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/shard-glk2/boot > .html>, PASS > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/ttm: never purge busy objects
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/7379 Lakshmi. -Original Message- From: Auld, Matthew Sent: Tuesday, November 8, 2022 5:49 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/ttm: never purge busy objects On 07/11/2022 17:57, Patchwork wrote: > *Patch Details* > *Series:* drm/i915/ttm: never purge busy objects > *URL:*https://patchwork.freedesktop.org/series/110601/ > <https://patchwork.freedesktop.org/series/110601/> > *State:* failure > *Details:* > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/index.html > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/index.htm > l> > > > CI Bug Log - changes from CI_DRM_12351 -> Patchwork_110601v1 > > > Summary > > *FAILURE* > > Serious unknown changes coming with Patchwork_110601v1 absolutely need > to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_110601v1, please notify your bug team 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_110601v1/index.html > > > Participating hosts (42 -> 30) > > Additional (2): fi-kbl-soraka fi-cml-u2 Missing (14): fi-ilk-m540 > fi-bdw-samus fi-tgl-dsi fi-hsw-4200u bat-dg2-9 > bat-adlp-6 bat-adlp-4 fi-ctg-p8600 bat-adln-1 bat-rplp-1 bat-rpls-1 > bat-rpls-2 bat-dg2-11 bat-jsl-1 > > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_110601v1: > > > IGT changes > > > Possible regressions > > * igt@i915_suspend@basic-s3-without-i915: > o fi-cml-u2: NOTRUN -> INCOMPLETE > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-cml-u2 > /igt@i915_susp...@basic-s3-without-i915.html> Unrelated. Patch only affects discrete platforms. > > > Known issues > > Here are the changes found in Patchwork_110601v1 that come from known > issues: > > > IGT changes > > > Issues hit > > * > > igt@gem_exec_fence@basic-busy@bcs0: > > o fi-cml-u2: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-cml-u2/igt@gem_exec_fence@basic-b...@bcs0.html> > (i915#1208 <https://gitlab.freedesktop.org/drm/intel/issues/1208>) +1 > similar issue > * > > igt@gem_exec_gttfill@basic: > > o > > fi-kbl-soraka: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-kbl-so > raka/igt@gem_exec_gttf...@basic.html> (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +8 similar > issues > > o > > fi-pnv-d510: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12351/fi-pnv-d510/igt > @gem_exec_gttf...@basic.html> -> FAIL > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-pnv-d5 > 10/igt@gem_exec_gttf...@basic.html> (i915#7229 > <https://gitlab.freedesktop.org/drm/intel/issues/7229>) > > * > > igt@gem_huc_copy@huc-copy: > > o > > fi-cml-u2: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-cml-u2 > /igt@gem_huc_c...@huc-copy.html> (i915#2190 > <https://gitlab.freedesktop.org/drm/intel/issues/2190>) > > o > > fi-kbl-soraka: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-kbl-so > raka/igt@gem_huc_c...@huc-copy.html> (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#2190 > <https://gitlab.freedesktop.org/drm/intel/issues/2190>) > > * > > igt@gem_lmem_swapping@basic: > > o fi-kbl-soraka: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-kbl-soraka/igt@gem_lmem_swapp...@basic.html> > (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / > i915#4613 <https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3 similar > issues > * > > igt@gem_lmem_swapping@verify-random: > > o fi-cml-u2: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v1/fi-cml-u2/igt@gem_lmem_swapp...@verify-random.html> > (i915#4613 <https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3 > similar issues >
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: header cleanups, again
Re-reported. -Original Message- From: Nikula, Jani Sent: Wednesday, November 2, 2022 8:17 AM To: Patchwork Cc: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: header cleanups, again On Wed, 02 Nov 2022, Patchwork wrote: > == Series Details == > > Series: drm/i915: header cleanups, again > URL : https://patchwork.freedesktop.org/series/110404/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_12331 -> Patchwork_110404v1 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_110404v1 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_110404v1, please notify your bug team 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_110404v1/index.html > > Participating hosts (40 -> 30) > -- > > Additional (2): fi-kbl-soraka fi-pnv-d510 > Missing(12): bat-dg2-8 bat-adlm-1 bat-dg2-9 bat-adlp-6 bat-adlp-4 > bat-adln-1 bat-atsm-1 bat-rplp-1 bat-rpls-1 bat-rpls-2 bat-dg2-11 bat-jsl-1 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_110404v1: > > ### IGT changes ### > > Possible regressions > > * igt@i915_selftest@live@gem_contexts: > - fi-kbl-soraka: NOTRUN -> [INCOMPLETE][1] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@i915_selftest@live@gem_contexts.html > This should be completely unrelated. > > Known issues > > > Here are the changes found in Patchwork_110404v1 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_exec_gttfill@basic: > - fi-kbl-soraka: NOTRUN -> [SKIP][2] ([fdo#109271]) +8 similar issues >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@gem_exec_gttf...@basic.html > > * igt@gem_huc_copy@huc-copy: > - fi-kbl-soraka: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#2190]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@gem_huc_c...@huc-copy.html > > * igt@gem_lmem_swapping@basic: > - fi-kbl-soraka: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#4613]) +3 > similar issues >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@gem_lmem_swapp...@basic.html > > * igt@i915_selftest@live@gt_heartbeat: > - fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][5] ([i915#5334]) >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@i915_selftest@live@gt_heartbeat.html > > * igt@i915_selftest@live@gt_pm: > - fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][6] ([i915#1886]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@i915_selftest@live@gt_pm.html > > * igt@kms_chamelium@common-hpd-after-suspend: > - fi-icl-u2: NOTRUN -> [SKIP][7] ([fdo#111827]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-icl-u2/ > igt@kms_chamel...@common-hpd-after-suspend.html > > * igt@kms_chamelium@hdmi-hpd-fast: > - fi-kbl-soraka: NOTRUN -> [SKIP][8] ([fdo#109271] / [fdo#111827]) > +7 similar issues >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-kbl-sor > aka/igt@kms_chamel...@hdmi-hpd-fast.html > > * > igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size: > - fi-bsw-kefka: [PASS][9] -> [FAIL][10] ([i915#6298]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12331/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cur...@atomic-transitions-varying-size.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-bsw-kef > ka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transiti > ons-varying-size.html > > * igt@kms_psr@primary_page_flip: > - fi-pnv-d510:NOTRUN -> [SKIP][11] ([fdo#109271]) +43 similar > issues >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110404v1/fi-pnv-d51 > 0/igt@kms_psr@primary_page_flip.html > > > Possible fixes > > * igt@i915_selftest@live@execlists: > - fi-icl-u2: [INCOMPLETE][12] ([i915#4890]) -&
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual (rev4)
Re-reproted.
From: Gupta, Anshuman
Sent: Friday, October 28, 2022 11:00 PM
To: Vudum, Lakshminarayana
Cc: intel-gfx@lists.freedesktop.org
Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915/dgfx: Grab wakeref at
i915_ttm_unmap_virtual (rev4)
Hi Lakshmi ,
Below CI failure are not related to this series.
Could you please re-report the results.
Br,
Anshuman Gupta.
From: Patchwork
mailto:patchw...@emeril.freedesktop.org>>
Sent: Thursday, October 27, 2022 8:11 PM
To: Gupta, Anshuman mailto:anshuman.gu...@intel.com>>
Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Subject: ✗ Fi.CI.BAT: failure for drm/i915/dgfx: Grab wakeref at
i915_ttm_unmap_virtual (rev4)
Patch Details
Series:
drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual (rev4)
URL:
https://patchwork.freedesktop.org/series/108972/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/index.html
CI Bug Log - changes from CI_DRM_12310 -> Patchwork_108972v4
Summary
FAILURE
Serious unknown changes coming with Patchwork_108972v4 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_108972v4, please notify your bug team 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_108972v4/index.html
Participating hosts (42 -> 39)
Additional (1): fi-kbl-soraka
Missing (4): fi-ctg-p8600 fi-hsw-4770 fi-rkl-11600 fi-icl-u2
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_108972v4:
IGT changes
Possible regressions
* igt@i915_selftest@live@gem_migrate:
* fi-kbl-soraka: NOTRUN ->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@i915_selftest@live@gem_migrate.html>
Known issues
Here are the changes found in Patchwork_108972v4 that come from known issues:
IGT changes
Issues hit
* igt@gem_exec_gttfill@basic:
* fi-kbl-soraka: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@gem_exec_gttf...@basic.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +9 similar
issues
* igt@gem_huc_copy@huc-copy:
* fi-kbl-soraka: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@gem_huc_c...@huc-copy.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
i915#2190<https://gitlab.freedesktop.org/drm/intel/issues/2190>)
* igt@gem_lmem_swapping@basic:
* fi-kbl-soraka: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@gem_lmem_swapp...@basic.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
i915#4613<https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3 similar
issues
* igt@gem_tiled_blits@basic:
* fi-pnv-d510:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12310/fi-pnv-d510/igt@gem_tiled_bl...@basic.html>
->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-pnv-d510/igt@gem_tiled_bl...@basic.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +2 similar
issues
* igt@i915_module_load@reload:
* fi-skl-guc:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12310/fi-skl-guc/igt@i915_module_l...@reload.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-skl-guc/igt@i915_module_l...@reload.html>
(i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>)
* igt@i915_selftest@live@gt_pm:
* fi-kbl-soraka: NOTRUN ->
DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html>
(i915#1886<https://gitlab.freedesktop.org/drm/intel/issues/1886>)
* igt@i915_selftest@live@hangcheck:
* fi-rkl-guc:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12310/fi-rkl-guc/igt@i915_selftest@l...@hangcheck.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-rkl-guc/igt@i915_selftest@l...@hangcheck.html>
(i915#4983<https://gitlab.freedesktop.org/drm/intel/issues/4983>)
* igt@kms_chamelium@hdmi-hpd-fast:
* fi-kbl-soraka: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108972v4/fi-kbl-soraka/igt@kms_chamel...@hdmi-hpd-fast.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +7 similar
issues
Possible fixes
* igt@gem_exec_suspend@basic-s3@smem:
* {bat-rplp-1}:
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12310/bat-rplp-1/igt@gem_exec_suspend@basic...@smem.
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: CAGF and RC6 changes for MTL (rev11)
Re-reported. -Original Message- From: Dixit, Ashutosh Sent: Tuesday, October 25, 2022 10:26 AM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: CAGF and RC6 changes for MTL (rev11) On Mon, 24 Oct 2022 18:25:06 -0700, Patchwork wrote: > Hi Lakshmi, The below failures are unrelated to this series. Thanks. -- Ashutosh > Patch Details > > Series: i915: CAGF and RC6 changes for MTL (rev11) > URL: https://patchwork.freedesktop.org/series/108156/ > State: failure > Details: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108156v11/index.htm > l > > CI Bug Log - changes from CI_DRM_12288 -> Patchwork_108156v11 > > Summary > > FAILURE > > Serious unknown changes coming with Patchwork_108156v11 absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_108156v11, please notify your bug team 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_108156v11/index.htm > l > > Participating hosts (41 -> 40) > > Additional (1): bat-atsm-1 > Missing (2): fi-ctg-p8600 fi-icl-u2 > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_108156v11: > > IGT changes > > Possible regressions > > • igt@gem_exec_parallel@engines@contexts: > > □ fi-bsw-nick: PASS -> INCOMPLETE > • igt@i915_selftest@live@hugepages: > > □ fi-cfl-8109u: PASS -> DMESG-FAIL > > □ fi-skl-guc: PASS -> DMESG-FAIL > > • igt@i915_suspend@basic-s3-without-i915: > > □ fi-rkl-11600: NOTRUN -> INCOMPLETE > > Suppressed
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Revert "drm/i915/uapi: expose GTT alignment"
Filed a new issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/7323
igt@i915_selftest@mock@requests - incomplete - GEM_BUG_ON(ce->timeline->seqno
!= ({ do { __attribute__((__noreturn__)) extern void __compiletime_assert,
kernel BUG at drivers/gpu/drm/i915/gt/intel_engine_pm.c:72!
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Wednesday, October 26, 2022 11:01 AM
To: Vudum, Lakshminarayana ;
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for Revert "drm/i915/uapi: expose GTT
alignment"
On 26/10/2022 18:53, Vudum, Lakshminarayana wrote:
> @Auld, Matthew Can you check if this is related to your patch? Looks new to
> me.
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl9/igt@i915_selftest@m...@requests.html#dmesg-warnings16
For sure unrelated to this series.
>
> Lakshmi.
> -Original Message-
> From: Auld, Matthew
> Sent: Wednesday, October 26, 2022 1:53 AM
> To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
>
> Subject: Re: ✗ Fi.CI.IGT: failure for Revert "drm/i915/uapi: expose GTT
> alignment"
>
> On 26/10/2022 08:47, Patchwork wrote:
>> *Patch Details*
>> *Series:*Revert "drm/i915/uapi: expose GTT alignment"
>> *URL:* https://patchwork.freedesktop.org/series/110041/
>> <https://patchwork.freedesktop.org/series/110041/>
>> *State:* failure
>> *Details:*
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.html
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.html>
>>
>>
>>CI Bug Log - changes from CI_DRM_12284_full -> Patchwork_110041v1_full
>>
>>
>> Summary
>>
>> *FAILURE*
>>
>> Serious unknown changes coming with Patchwork_110041v1_full absolutely
>> need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_110041v1_full, please notify your bug team to
>> allow them
>> to document this new failure mode, which will reduce false positives in CI.
>>
>>
>> Participating hosts (11 -> 11)
>>
>> No changes in participating hosts
>>
>>
>> Possible new issues
>>
>> Here are the unknown changes that may have been introduced in
>> Patchwork_110041v1_full:
>>
>>
>>IGT changes
>>
>>
>> Possible regressions
>>
>>*
>>
>> igt@i915_pm_rpm@drm-resources-equal:
>>
>>o shard-iclb: PASS
>>
>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-iclb3/igt@i915_pm_...@drm-resources-equal.html>
>> -> FAIL
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-iclb8/igt@i915_pm_...@drm-resources-equal.html>
>>*
>>
>> igt@i915_selftest@live@guc_hang:
>>
>>o shard-skl: PASS
>>
>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-skl9/igt@i915_selftest@live@guc_hang.html>
>> -> INCOMPLETE
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl6/igt@i915_selftest@live@guc_hang.html>
>>*
>>
>> igt@i915_suspend@forcewake:
>>
>>o shard-skl: NOTRUN -> INCOMPLETE
>>
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl4/igt@i915_susp...@forcewake.html>
>> +1 similar issue
>>
>>
>
>
> All look to be unrelated.
>
>> Warnings
>>
>>*
>>
>> igt@kms_color@ctm-0-75@pipe-d-edp-1:
>>
>>o shard-tglb: FAIL
>>
>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-tglb6/igt@kms_color@ctm-0...@pipe-d-edp-1.html>
>> (i915#315 <https://gitlab.freedesktop.org/drm/intel/issues/315> / i915#6946
>> <https://gitlab.freedesktop.org/drm/intel/issues/6946>) -> INCOMPLETE
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-tglb8/igt@kms_color@ctm-0...@pipe-d-edp-1.html>
>>*
>>
>> igt@kms_cursor_legacy@flip-vs-cursor@atomic:
>>
>>o shard-skl: FAIL
>>
>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-skl6/igt@kms_cursor_legacy@flip-vs-cur...@atomic.html>
>> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>) ->
>> INCOMPLETE
>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl9/igt@kms_cursor_legacy@flip-vs-cur...@atomic.html>
>>
>>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Revert "drm/i915/uapi: expose GTT alignment"
@Auld, Matthew Can you check if this is related to your patch? Looks new to me.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl9/igt@i915_selftest@m...@requests.html#dmesg-warnings16
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Wednesday, October 26, 2022 1:53 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for Revert "drm/i915/uapi: expose GTT
alignment"
On 26/10/2022 08:47, Patchwork wrote:
> *Patch Details*
> *Series:* Revert "drm/i915/uapi: expose GTT alignment"
> *URL:*https://patchwork.freedesktop.org/series/110041/
> <https://patchwork.freedesktop.org/series/110041/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.html>
>
>
> CI Bug Log - changes from CI_DRM_12284_full -> Patchwork_110041v1_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_110041v1_full absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_110041v1_full, please notify your bug team to
> allow them
> to document this new failure mode, which will reduce false positives in CI.
>
>
> Participating hosts (11 -> 11)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_110041v1_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@i915_pm_rpm@drm-resources-equal:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-iclb3/igt@i915_pm_...@drm-resources-equal.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-iclb8/igt@i915_pm_...@drm-resources-equal.html>
> *
>
> igt@i915_selftest@live@guc_hang:
>
> o shard-skl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-skl9/igt@i915_selftest@live@guc_hang.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl6/igt@i915_selftest@live@guc_hang.html>
> *
>
> igt@i915_suspend@forcewake:
>
> o shard-skl: NOTRUN -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl4/igt@i915_susp...@forcewake.html>
> +1 similar issue
>
>
All look to be unrelated.
> Warnings
>
> *
>
> igt@kms_color@ctm-0-75@pipe-d-edp-1:
>
> o shard-tglb: FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-tglb6/igt@kms_color@ctm-0...@pipe-d-edp-1.html>
> (i915#315 <https://gitlab.freedesktop.org/drm/intel/issues/315> / i915#6946
> <https://gitlab.freedesktop.org/drm/intel/issues/6946>) -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-tglb8/igt@kms_color@ctm-0...@pipe-d-edp-1.html>
> *
>
> igt@kms_cursor_legacy@flip-vs-cursor@atomic:
>
> o shard-skl: FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-skl6/igt@kms_cursor_legacy@flip-vs-cur...@atomic.html>
> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>) ->
> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-skl9/igt@kms_cursor_legacy@flip-vs-cur...@atomic.html>
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> *
>
> igt@gem_mmap_offset@clear@smem0:
>
> o {shard-rkl}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-rkl-4/igt@gem_mmap_offset@cl...@smem0.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-rkl-5/igt@gem_mmap_offset@cl...@smem0.html>
> *
>
> igt@i915_pm_rc6_residency@rc6-idle@vcs0:
>
> o {shard-rkl}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-rkl-4/igt@i915_pm_rc6_residency@rc6-i...@vcs0.html>
> -> WARN
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/shard-rkl-5/igt@i915_pm_rc6_residency@rc6-i...@vcs0.html>
> *
>
> igt@i915_pm_rc6_residency@rc6-idle@vecs0:
>
> o {shard-rkl}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/shard-rkl-4/igt@i915_pm_rc
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/xelp: Add Wa_1806527549 (rev2)
Filed a new issue and re-reported. Rest are known issues. https://gitlab.freedesktop.org/drm/intel/-/issues/7320 -Original Message- From: Sousa, Gustavo Sent: Tuesday, October 25, 2022 2:55 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/xelp: Add Wa_1806527549 (rev2) On Thu, Oct 20, 2022 at 01:00:27AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/xelp: Add Wa_1806527549 (rev2) > URL : https://patchwork.freedesktop.org/series/109885/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_12261_full -> Patchwork_109885v2_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_109885v2_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_109885v2_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (9 -> 12) > -- > > Additional (3): shard-rkl shard-dg1 shard-tglu > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_109885v2_full: > > ### IGT changes ### > > Possible regressions > > * igt@i915_selftest@live@mman: > - shard-skl: NOTRUN -> [INCOMPLETE][1] +1 similar issue >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl2/igt@i915_selftest@l...@mman.html Not related to this patch, as the workaround does not target this platform. > > * igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip: > - shard-iclb: [PASS][2] -> [FAIL][3] >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-iclb8/igt@kms_big...@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip.html >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-iclb2/igt@kms_big...@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip.html Existing issue: http://gfx-ci.fi.intel.com/cibuglog-ng/issue/7783 > > * igt@kms_plane_lowres@tiling-none@pipe-b-hdmi-a-1: > - shard-glk: [PASS][4] -> [FAIL][5] >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-glk9/igt@kms_plane_lowres@tiling-n...@pipe-b-hdmi-a-1.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-glk3/igt@kms_plane_lowres@tiling-n...@pipe-b-hdmi-a-1.html Maybe related to http://gfx-ci.fi.intel.com/cibuglog-ng/issue/7841 ? Nevertheless, not related to this patch, as the workaround does not target this platform. > > > Warnings > > * igt@runner@aborted: > - shard-skl: ([FAIL][6], [FAIL][7], [FAIL][8], [FAIL][9], > [FAIL][10]) ([i915#3002] / [i915#4312] / [i915#6949]) -> ([FAIL][11], > [FAIL][12], [FAIL][13], [FAIL][14], [FAIL][15], [FAIL][16], [FAIL][17], > [FAIL][18]) ([i915#3002] / [i915#4312]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-skl4/igt@run...@aborted.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-skl6/igt@run...@aborted.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-skl2/igt@run...@aborted.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-skl6/igt@run...@aborted.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/shard-skl10/igt@run...@aborted.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl5/igt@run...@aborted.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl5/igt@run...@aborted.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl10/igt@run...@aborted.html >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl7/igt@run...@aborted.html >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl10/igt@run...@aborted.html >[16]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl4/igt@run...@aborted.html >[17]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl1/igt@run...@aborted.html >[18]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109885v2/shard-skl2/igt@run...@aborted.html > > > Suppressed > > The following results come from untrusted machines, tests, or statuses. > They do not affect the overall result. > > * igt@gem_pwr
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Revert "drm/i915/uapi: expose GTT alignment"
Regression failures are related to
https://gitlab.freedesktop.org/drm/intel/-/issues/7311
Re-reported.
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Tuesday, October 25, 2022 2:09 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for Revert "drm/i915/uapi: expose GTT
alignment"
On 24/10/2022 12:55, Patchwork wrote:
> *Patch Details*
> *Series:* Revert "drm/i915/uapi: expose GTT alignment"
> *URL:*https://patchwork.freedesktop.org/series/110041/
> <https://patchwork.freedesktop.org/series/110041/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/index.htm
> l>
>
>
> CI Bug Log - changes from CI_DRM_12284 -> Patchwork_110041v1
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_110041v1 absolutely need
> to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_110041v1, please notify your bug team 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_110041v1/index.html
>
>
> Participating hosts (41 -> 41)
>
> Additional (3): fi-hsw-4770 fi-icl-u2 bat-atsm-1 Missing (3):
> fi-ctg-p8600 fi-bdw-samus fi-tgl-dsi
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_110041v1:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@i915_selftest@live@hugepages:
>
> o
>
> fi-glk-j4005: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/fi-glk-j4005/ig
> t@i915_selftest@l...@hugepages.html> -> DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-glk-j4
> 005/igt@i915_selftest@l...@hugepages.html>
>
> o
>
> fi-rkl-guc: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/fi-rkl-guc/igt@
> i915_selftest@l...@hugepages.html> -> DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-rkl-gu
> c/igt@i915_selftest@l...@hugepages.html>
>
> o
>
> fi-icl-u2: NOTRUN -> DMESG-FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-icl-u2
> /igt@i915_selftest@l...@hugepages.html>
>
These failures are unrelated.
https://gitlab.freedesktop.org/drm/intel/-/issues/7311
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_parallel@engines@contexts:
> o {fi-ehl-2}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/fi-ehl-2/igt@ge
> m_exec_parallel@engi...@contexts.html> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-ehl-2/
> igt@gem_exec_parallel@engi...@contexts.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_110041v1 that come from known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_exec_gttfill@basic:
>
> o fi-pnv-d510: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/fi-pnv-d510/igt@gem_exec_gttf...@basic.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-pnv-d510/igt@gem_exec_gttf...@basic.html>
> (i915#7229 <https://gitlab.freedesktop.org/drm/intel/issues/7229>)
> *
>
> igt@gem_huc_copy@huc-copy:
>
> o fi-icl-u2: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-icl-u2/igt@gem_huc_c...@huc-copy.html>
> (i915#2190 <https://gitlab.freedesktop.org/drm/intel/issues/2190>)
> *
>
> igt@gem_lmem_swapping@random-engines:
>
> o fi-icl-u2: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110041v1/fi-icl-u2/igt@gem_lmem_swapp...@random-engines.html>
> (i915#4613 <https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3
> similar issues
> *
>
> igt@gem_render_tiled_blits@basic:
>
> o fi-apl-guc: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12284/fi-apl-guc/igt@gem_render_tiled_bl...@basic.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.or
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/xelpg: Fix write to MTL_MCR_SELECTOR
Correct. Re-reported.
-Original Message-
From: Roper, Matthew D
Sent: Thursday, October 20, 2022 7:50 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/xelpg: Fix write to
MTL_MCR_SELECTOR
On Wed, Oct 19, 2022 at 11:43:05PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/xelpg: Fix write to MTL_MCR_SELECTOR
> URL : https://patchwork.freedesktop.org/series/109912/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12261 -> Patchwork_109912v1
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_109912v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_109912v1, please notify your bug team 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_109912v1/index.html
>
> Participating hosts (42 -> 41)
> --
>
> Additional (1): fi-rkl-11600
> Missing(2): fi-kbl-soraka fi-cml-u2
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_109912v1:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_pm_rpm@basic-pci-d3-state:
> - bat-adlp-4: [PASS][1] -> [DMESG-WARN][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/bat-adlp-4/igt@i915_pm_...@basic-pci-d3-state.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/bat-adlp-4
> /igt@i915_pm_...@basic-pci-d3-state.html
WARNING: possible circular locking dependency detected
Seems to be the same deadlock reported in
https://gitlab.freedesktop.org/drm/intel/-/issues/7077 just on a different
subtest.
>
> * igt@i915_selftest@live@gem_contexts:
> - fi-kbl-7567u: [PASS][3] -> [DMESG-FAIL][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/fi-kbl-7567u/igt@i915_selftest@live@gem_contexts.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-kbl-756
> 7u/igt@i915_selftest@live@gem_contexts.html
https://gitlab.freedesktop.org/drm/intel/-/issues/7270
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_selftest@live@migrate:
> - {bat-adlp-6}: [PASS][5] -> [INCOMPLETE][6]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/bat-adlp-6/igt@i915_selftest@l...@migrate.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/bat-adlp-6
> /igt@i915_selftest@l...@migrate.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_109912v1 that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_huc_copy@huc-copy:
> - fi-rkl-11600: NOTRUN -> [SKIP][7] ([i915#2190])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-rkl-116
> 00/igt@gem_huc_c...@huc-copy.html
>
> * igt@gem_lmem_swapping@basic:
> - fi-rkl-11600: NOTRUN -> [SKIP][8] ([i915#4613]) +3 similar issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-rkl-116
> 00/igt@gem_lmem_swapp...@basic.html
>
> * igt@gem_tiled_pread_basic:
> - fi-rkl-11600: NOTRUN -> [SKIP][9] ([i915#3282])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-rkl-116
> 00/igt@gem_tiled_pread_basic.html
>
> * igt@i915_pm_backlight@basic-brightness:
> - fi-rkl-11600: NOTRUN -> [SKIP][10] ([i915#3012])
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-rkl-116
> 00/igt@i915_pm_backli...@basic-brightness.html
>
> * igt@i915_selftest@live@gt_heartbeat:
> - fi-bdw-5557u: [PASS][11] -> [DMESG-FAIL][12] ([i915#5334])
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12261/fi-bdw-5557u/igt@i915_selftest@live@gt_heartbeat.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-bdw-555
> 7u/igt@i915_selftest@live@gt_heartbeat.html
>
> * igt@i915_suspend@basic-s3-without-i915:
> - fi-rkl-11600: NOTRUN -> [INCOMPLETE][13] ([i915#5982])
>[13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109912v1/fi-rkl-116
> 00/igt@i915_susp...@basic-s3-without
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Explicit MCR handling and MTL steering (rev4)
Filed a new issue and re-reported. https://gitlab.freedesktop.org/drm/intel/-/issues/7230 igt@kms_async_flips@async-flip-with-page-flip-events@.* - fail - Failed assertion: (fps / 1000) > (data->refresh_rate * MIN_FLIPS_PER_FRAME), FPS should be significantly higher than the refresh rate Lakshmi. -Original Message- From: Roper, Matthew D Sent: Monday, October 17, 2022 9:18 AM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for Explicit MCR handling and MTL steering (rev4) On Sat, Oct 15, 2022 at 01:03:31AM +, Patchwork wrote: > == Series Details == > > Series: Explicit MCR handling and MTL steering (rev4) > URL : https://patchwork.freedesktop.org/series/108755/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_12242_full -> Patchwork_108755v4_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_108755v4_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_108755v4_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (9 -> 11) > -- > > Additional (2): shard-rkl shard-dg1 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_108755v4_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_async_flips@async-flip-with-page-flip-events@pipe-c-edp-1: > - shard-skl: [PASS][1] -> [FAIL][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@kms_async_flips@async-flip-with-page-flip-eve...@pipe-c-edp-1.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108755v4/shard-skl3 > /igt@kms_async_flips@async-flip-with-page-flip-eve...@pipe-c-edp-1.htm > l GT multicast register handling wouldn't have changed the behavior of a SKL display test. This failure is unrelated. Other subtests of this test also seem to be sporadically failing in a similar manner. This might be related to the same root cause as fdo#2521. Matt > > > Warnings > > * igt@runner@aborted: > - shard-skl: ([FAIL][3], [FAIL][4], [FAIL][5], [FAIL][6]) > ([i915#3002] / [i915#4312] / [i915#6949]) -> ([FAIL][7], [FAIL][8], > [FAIL][9]) ([i915#3002] / [i915#4312]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@run...@aborted.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@run...@aborted.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/igt@run...@aborted.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/igt@run...@aborted.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108755v4/shard-skl1/igt@run...@aborted.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108755v4/shard-skl2/igt@run...@aborted.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108755v4/shard-skl7 > /igt@run...@aborted.html > > > Known issues > > > Here are the changes found in Patchwork_108755v4_full that come from known > issues: > > ### CI changes ### > > Possible fixes > > * boot: > - shard-skl: ([PASS][10], [PASS][11], [PASS][12], [PASS][13], > [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], > [PASS][20], [FAIL][21], [PASS][22], [FAIL][23], [PASS][24], [PASS][25], > [PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31], > [PASS][32], [PASS][33], [PASS][34]) ([i915#5032]) -> ([PASS][35], [PASS][36], > [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], > [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], > [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54], > [PASS][55], [PASS][56], [PASS][57]) >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html >[15]: > https://
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix simulated GPU reset wrt. encoder HW readout
Re-reported.
-Original Message-
From: Deak, Imre
Sent: Saturday, October 8, 2022 1:10 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Cc: Ville Syrjälä
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Fix simulated GPU reset wrt.
encoder HW readout
On Fri, Oct 07, 2022 at 03:09:21PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix simulated GPU reset wrt. encoder HW readout
> URL : https://patchwork.freedesktop.org/series/109480/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12225 -> Patchwork_109480v1
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_109480v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_109480v1, please notify your bug team 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_109480v1/index.html
>
> Participating hosts (46 -> 44)
> --
>
> Additional (1): fi-tgl-dsi
> Missing(3): fi-ctg-p8600 fi-hsw-4770 fi-hsw-4200u
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_109480v1:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@live@execlists:
> - fi-bsw-nick:[PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12225/fi-bsw-nick/igt@i915_selftest@l...@execlists.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/fi-bsw-nic
> k/igt@i915_selftest@l...@execlists.html
The change would have an effect only during the
igt@kms_busy@extended-pageflip-modeset-hang-oldfb test, but it was not run, so
I think the above failure is unrelated.
>
> Known issues
>
>
> Here are the changes found in Patchwork_109480v1 that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@kms_chamelium@common-hpd-after-suspend:
> - bat-dg1-5: NOTRUN -> [SKIP][3] ([fdo#111827])
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-dg1-5/igt@kms_chamel...@common-hpd-after-suspend.html
> - fi-bdw-5557u: NOTRUN -> [SKIP][4] ([fdo#109271] / [fdo#111827])
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/fi-bdw-555
> 7u/igt@kms_chamel...@common-hpd-after-suspend.html
>
> * igt@kms_pipe_crc_basic@suspend-read-crc:
> - bat-dg1-5: NOTRUN -> [SKIP][5] ([i915#4078])
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-dg1-5/
> igt@kms_pipe_crc_ba...@suspend-read-crc.html
>
> * igt@runner@aborted:
> - fi-bsw-nick:NOTRUN -> [FAIL][6] ([fdo#109271] / [i915#4312])
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/fi-bsw-nic
> k/igt@run...@aborted.html
>
>
> Possible fixes
>
> * igt@fbdev@read:
> - {bat-rpls-2}: [SKIP][7] ([i915#2582]) -> [PASS][8] +4 similar
> issues
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12225/bat-rpls-2/igt@fb...@read.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-rpls-2
> /igt@fb...@read.html
>
> * igt@gem_exec_suspend@basic-s3@lmem0:
> - {bat-dg2-11}: [DMESG-WARN][9] ([i915#6816]) -> [PASS][10]
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12225/bat-dg2-11/igt@gem_exec_suspend@basic...@lmem0.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-dg2-11
> /igt@gem_exec_suspend@basic...@lmem0.html
>
> * igt@gem_exec_suspend@basic-s3@smem:
> - {bat-rpls-1}: [DMESG-WARN][11] ([i915#6687]) -> [PASS][12]
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12225/bat-rpls-1/igt@gem_exec_suspend@basic...@smem.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-rpls-1
> /igt@gem_exec_suspend@basic...@smem.html
>
> * igt@gem_huc_copy@huc-copy:
> - {bat-atsm-1}: [FAIL][13] ([i915#7029]) -> [PASS][14]
>[13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12225/bat-atsm-1/igt@gem_huc_c...@huc-copy.html
>[14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109480v1/bat-atsm-1
> /igt@gem_huc_c...@huc-copy.html
>
> * igt@i915_module_load@load:
> - {bat-atsm-1}: [DMESG-WARN][15] ([i
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: disable FBC if its pipe is fused off
Re-reported. -Original Message- From: Saarinen, Jani Sent: Wednesday, September 28, 2022 12:09 AM To: Coelho, Luciano ; intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: RE: ✗ Fi.CI.IGT: failure for drm/i915: disable FBC if its pipe is fused off +Lakshmi. > -Original Message- > From: Intel-gfx On Behalf Of > Coelho, Luciano > Sent: tiistai 27. syyskuuta 2022 14.28 > To: intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: disable > FBC if its pipe is fused off > > Hi, > > This failure is not a real issue. For some reason the > igt@kms_writeback@writeback-check-output test was not running before > and now it is. The test is always getting skipped (even in local > tests), so this result is as expected. The test is also skipped without this > patch. > > This failure can be ignored. > > -- > Cheers, > Luca. > > On Mon, 2022-09-26 at 19:13 +, Patchwork wrote: > > Patch Details > Series:drm/i915: disable FBC if its pipe is fused off > URL: https://patchwork.freedesktop.org/series/109044/ > State: failure > Details: https://intel-gfx-ci.01.org/tree/drm- > tip/Patchwork_109044v1/index.html > > CI Bug Log - changes from CI_DRM_12182_full -> > Patchwork_109044v1_full > > > Summary > > > FAILURE > > Serious unknown changes coming with Patchwork_109044v1_full > absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_109044v1_full, please notify your bug team to > allow them > to document this new failure mode, which will reduce false positives > in CI. > > > Participating hosts (9 -> 11) > > > Additional (2): shard-rkl shard-tglu > > > Possible new issues > > > Here are the unknown changes that may have been introduced in > Patchwork_109044v1_full: > > > IGT changes > > > Possible regressions > > > * igt@kms_writeback@writeback-check-output: > > * shard-tglb: NOTRUN -> SKIP <https://intel-gfx- > ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > tglb7/igt@kms_writeb...@writeback-check-output.html> > > > Known issues > > > Here are the changes found in Patchwork_109044v1_full that come from > known issues: > > > CI changes > > > IGT changes > > > Issues hit > > > * igt@gem_eio@wait-immediate: > > * shard-apl: PASS <https://intel-gfx-ci.01.org/tree/drm- > tip/CI_DRM_12182/shard-apl6/igt@gem_...@wait-immediate.html> -> > DMESG- WARN > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > apl2/igt@gem_...@wait-immediate.html> (i915#62 > <https://gitlab.freedesktop.org/drm/intel/issues/62> ) +13 similar > issues > > * igt@gem_exec_balancer@parallel: > > * shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm- > tip/CI_DRM_12182/shard-iclb1/igt@gem_exec_balan...@parallel.html> -> > SKIP > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > iclb5/igt@gem_exec_balan...@parallel.html> (i915#4525 > <https://gitlab.freedesktop.org/drm/intel/issues/4525> ) +1 similar > issue > > * igt@gem_exec_fair@basic-none@bcs0: > > * shard-tglb: NOTRUN -> FAIL <https://intel-gfx- > ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > tglb7/igt@gem_exec_fair@basic-n...@bcs0.html> (i915#2842 > <https://gitlab.freedesktop.org/drm/intel/issues/2842> ) +4 similar > issues > > * igt@gem_exec_fair@basic-pace@vecs0: > > * shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm- > tip/CI_DRM_12182/shard-iclb7/igt@gem_exec_fair@basic-p...@vecs0.html> > -> FAIL > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > iclb5/igt@gem_exec_fair@basic-p...@vecs0.html> (i915#2842 > <https://gitlab.freedesktop.org/drm/intel/issues/2842> ) > > * igt@gem_huc_copy@huc-copy: > > * shard-tglb: PASS <https://intel-gfx-ci.01.org/tree/drm- > tip/CI_DRM_12182/shard-tglb5/igt@gem_huc_c...@huc-copy.html> -> SKIP > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109044v1/shard- > tglb7/igt@gem_huc_c...@huc-copy.html> (i915#2190 > <https://gitlab.freedesktop.org/drm/intel/issues/2190> ) > > * igt@gem_
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Improvements to stolen memory setup (rev3)
Filed a new issue and reported the results. https://gitlab.freedesktop.org/drm/intel/-/issues/6898 Lakshmi. -Original Message- From: De Marchi, Lucas Sent: Thursday, September 22, 2022 6:55 AM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Improvements to stolen memory setup (rev3) On Sat, Sep 17, 2022 at 12:25:30AM +, Patchwork wrote: >== Series Details == > >Series: drm/i915: Improvements to stolen memory setup (rev3) >URL : https://patchwork.freedesktop.org/series/108620/ >State : failure > >== Summary == > >CI Bug Log - changes from CI_DRM_12146_full -> Patchwork_108620v3_full > > >Summary >--- > > **FAILURE** > > Serious unknown changes coming with Patchwork_108620v3_full > absolutely need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_108620v3_full, please notify your bug team to > allow them to document this new failure mode, which will reduce false > positives in CI. > > > >Participating hosts (10 -> 10) >-- > > No changes in participating hosts > >Possible new issues >--- > > Here are the unknown changes that may have been introduced in > Patchwork_108620v3_full: > >### IGT changes ### > > Possible regressions > > * igt@kms_plane_alpha_blend@pipe-d-alpha-7efc: >- shard-tglb: [PASS][1] -> [INCOMPLETE][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12146/shard-tglb3/igt@kms_plane_alpha_bl...@pipe-d-alpha-7efc.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108620v3/shard-tglb > 8/igt@kms_plane_alpha_bl...@pipe-d-alpha-7efc.html unrelated failure in display Lucas De Marchi
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Introduce struct cdclk_step
Filed a couple of issues and re-reported.
This one Likely a regression?
https://gitlab.freedesktop.org/drm/intel/-/issues/6864
Few tests - dmesg-warn/dmesg-fail/incomplete -BUG: unable to handle page fault
for address .*, #PF: supervisor read access in kernel mode, RIP:
0010:__list_add_valid, Call Trace: dma_fence_default_wait,
dma_fence_add_callback
https://gitlab.freedesktop.org/drm/intel/-/issues/6863
igt@debugfs_test@read_all_entries - incomplete - BUG: unable to handle page
fault for address: c9bb81a8, RIP: 0010:gen2_read32
Lakshmi.
-Original Message-
From: Dixit, Ashutosh
Sent: Friday, September 16, 2022 7:08 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Cc: Srivatsa, Anusha
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Introduce struct cdclk_step
On Fri, 16 Sep 2022 18:35:13 -0700, Patchwork wrote:
>
Hi Lakshmi,
> Series: Introduce struct cdclk_step
> URL: https://patchwork.freedesktop.org/series/108685/
> State: failure
> Details:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108685v1/index.html
>
> CI Bug Log - changes from CI_DRM_12148 -> Patchwork_108685v1
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_108685v1 absolutely need
> to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_108685v1, please notify your bug team 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_108685v1/index.html
>
> Participating hosts (43 -> 41)
>
> Additional (2): fi-icl-u2 fi-pnv-d510
> Missing (4): fi-ctg-p8600 fi-hsw-4200u fi-bdw-samus bat-dg1-5
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_108685v1:
>
> IGT changes
>
> Possible regressions
>
> • igt@debugfs_test@read_all_entries:
> □ fi-pnv-d510: NOTRUN -> INCOMPLETE
This failure is unrelated and needs a new bug. Seems to be caused by:
fe5979665f640 ("drm/i915/debugfs: Add perf_limit_reasons in debugfs")
Thanks.
--
Ashutosh
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/DG{1, 2}: FIXME Temporary hammer to disable rpm (rev2)
https://gitlab.freedesktop.org/drm/intel/-/issues/6844
[DG1][DG2] igt@i915_pm_rpm@.* - skip - Test requirement: has_runtime_pm, Last
errno: 5, Input/output error, SKIP
Issue closed as expected and re-reported.
Lakshmi.
-Original Message-
From: Gupta, Anshuman
Sent: Wednesday, September 14, 2022 9:10 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
; Vivi, Rodrigo
Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915/DG{1, 2}: FIXME Temporary hammer
to disable rpm (rev2)
> -Original Message-
> From: Gupta, Anshuman
> Sent: Wednesday, September 14, 2022 9:36 PM
> To: intel-gfx@lists.freedesktop.org; ",
> lakshminarayana.vudum"@intel.com; ",rodrigo.vivi"@intel.com
> Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/DG{1, 2}: FIXME
> Temporary hammer to disable rpm (rev2)
>
>
>
> On 9/14/2022 9:13 PM, Patchwork wrote:
> > *Patch Details*
> > *Series:* drm/i915/DG{1, 2}: FIXME Temporary hammer to disable rpm
> (rev2)
> > *URL:* https://patchwork.freedesktop.org/series/108477/
> > <https://patchwork.freedesktop.org/series/108477/>
> > *State:*failure
> > *Details:*
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108477v2/index.ht
> > ml
> > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108477v2/index.h
> > tm
> > l>
> >
> >
> > CI Bug Log - changes from CI_DRM_12134 -> Patchwork_108477v2
> >
> >
> > Summary
> >
> > *FAILURE*
> >
> > Serious unknown changes coming with Patchwork_108477v2 absolutely
> > need to be verified manually.
> >
> > If you think the reported changes have nothing to do with the
> > changes introduced in Patchwork_108477v2, please notify your bug
> > team 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_108477v2/index.ht
> > ml
> >
> >
> > Participating hosts (40 -> 41)
> >
> > Additional (5): fi-icl-u2 bat-dg2-9 bat-adln-1 bat-rplp-1 bat-jsl-1
> > Missing (4): fi-ctg-p8600 fi-hsw-4770 fi-rkl-11600 fi-tgl-dsi
> >
> >
> > Possible new issues
> >
> > Here are the unknown changes that may have been introduced in
> > Patchwork_108477v2:
> >
> >
> > IGT changes
> >
> >
> > Possible regressions
> >
> > * igt@i915_pm_rpm@module-reload:
> > o bat-dg1-5: PASS
> >
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12134/bat-dg1-5/igt
> > @i 915_pm_...@module-reload.html> -> SKIP
> > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108477v2/bat-dg1
> > -5 /igt@i915_pm_...@module-reload.html> +2 similar issues
> Hi Lakshmi ,
> With this series i915_pm_rpm test are expected to fail on DG1/DG2 as
> this patch disables runtime PM.
> Could you please re-report the result so that BAT can resume.
> Thanks,
> Anshuman Gupta.
> >
> >
> > Suppressed
> >
> > The following results come from untrusted machines, tests, or statuses.
> > They do not affect the overall result.
> >
> > *
> >
> > igt@i915_pm_rpm@basic-pci-d3-state:
> >
> > o {bat-dg2-8}: PASS
> >
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12134/bat-dg2-
> 8/igt@i915_pm_...@basic-pci-d3-state.html> -> SKIP <https://intel-gfx-
> ci.01.org/tree/drm-tip/Patchwork_108477v2/bat-dg2-
> 8/igt@i915_pm_...@basic-pci-d3-state.html> +2 similar issues
> > *
> >
> > igt@i915_pm_rpm@basic-rte:
> >
> > o {bat-dg2-9}: NOTRUN -> SKIP
> >
> > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108477v2/bat-dg2
> > -9 /igt@i915_pm_...@basic-rte.html> +2 similar issues
> >
> >
> > Known issues
> >
> > Here are the changes found in Patchwork_108477v2 that come from
> > known
> > issues:
> >
> >
> > IGT changes
> >
> >
> > Issues hit
> >
> > *
> >
> > igt@gem_huc_copy@huc-copy:
> >
> > o fi-icl-u2: NOTRUN -> SKIP
> >
> > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108477v2/fi-icl-
> u2/igt@gem_huc_c...@huc-copy.html> (i915#2190
> <https://gitlab.freedesktop.org/drm/intel/issues/2190>)
> > *
> >
> > igt@gem_lmem_swapping@random-engines:
> >
> > o fi-icl-u2: NOTRUN -> SKIP
> >
> > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_1
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Add "standalone media" support for MTL (rev4)
Re-reported. -Original Message- From: Roper, Matthew D Sent: Tuesday, September 6, 2022 10:28 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for i915: Add "standalone media" support for MTL (rev4) On Wed, Sep 07, 2022 at 04:06:23AM +, Patchwork wrote: > == Series Details == > > Series: i915: Add "standalone media" support for MTL (rev4) > URL : https://patchwork.freedesktop.org/series/107908/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_12083_full -> Patchwork_107908v4_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_107908v4_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_107908v4_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (11 -> 12) > -- > > Additional (1): shard-rkl > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_107908v4_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_ctx_exec@basic-close-race: > - shard-tglb: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12083/shard-tglb1/igt@gem_ctx_e...@basic-close-race.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-tglb > 5/igt@gem_ctx_e...@basic-close-race.html Unexpected incomplete with no errors. Does not appear to be related to this series. Matt > > > Known issues > > > Here are the changes found in Patchwork_107908v4_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_eio@unwedge-stress: > - shard-tglb: [PASS][3] -> [TIMEOUT][4] ([i915#3063]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12083/shard-tglb5/igt@gem_...@unwedge-stress.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-tglb > 3/igt@gem_...@unwedge-stress.html > > * igt@gem_exec_balancer@parallel-out-fence: > - shard-iclb: [PASS][5] -> [SKIP][6] ([i915#4525]) +2 similar > issues >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12083/shard-iclb4/igt@gem_exec_balan...@parallel-out-fence.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-iclb > 3/igt@gem_exec_balan...@parallel-out-fence.html > > * igt@gem_exec_fair@basic-deadline: > - shard-glk: [PASS][7] -> [FAIL][8] ([i915#2846]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12083/shard-glk2/igt@gem_exec_f...@basic-deadline.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-glk1 > /igt@gem_exec_f...@basic-deadline.html > > * igt@gem_exec_fair@basic-none-solo@rcs0: > - shard-apl: [PASS][9] -> [FAIL][10] ([i915#2842]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12083/shard-apl2/igt@gem_exec_fair@basic-none-s...@rcs0.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-apl1 > /igt@gem_exec_fair@basic-none-s...@rcs0.html > > * igt@gem_exec_fair@basic-pace@vcs1: > - shard-iclb: NOTRUN -> [FAIL][11] ([i915#2842]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-iclb > 1/igt@gem_exec_fair@basic-p...@vcs1.html > > * igt@gem_lmem_swapping@verify-random-ccs: > - shard-tglb: NOTRUN -> [SKIP][12] ([i915#4613]) >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-tglb > 2/igt@gem_lmem_swapp...@verify-random-ccs.html > > * igt@gem_pxp@create-regular-context-1: > - shard-tglb: NOTRUN -> [SKIP][13] ([i915#4270]) >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-tglb > 2/igt@gem_...@create-regular-context-1.html > > * igt@gen3_render_mixed_blits: > - shard-iclb: NOTRUN -> [SKIP][14] ([fdo#109289]) +1 similar issue >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107908v4/shard-iclb > 5/igt@gen3_render_mixed_blits.html > > * igt@gen7_exec_parse@basic-allocation: > - shard-tglb: NOTRUN -> [SKIP][15] ([fdo#109289]) >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwor
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/d13: Fix unclaimed accesses while loading PIPEDMC-C/D
Couple of bugs filed for these failures and re-reported. https://gitlab.freedesktop.org/drm/intel/-/issues/6576 https://gitlab.freedesktop.org/drm/intel/-/issues/6575 Thanks, Lakshmi. -Original Message- From: Deak, Imre Sent: Monday, August 15, 2022 1:50 AM To: intel-gfx@lists.freedesktop.org; Murthy, Arun R Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/d13: Fix unclaimed accesses while loading PIPEDMC-C/D On Mon, Aug 08, 2022 at 02:42:22PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/d13: Fix unclaimed accesses while loading PIPEDMC-C/D > URL : https://patchwork.freedesktop.org/series/107059/ > State : failure Thanks for the review pushed to drm-intel-next. The failure below is unrelated as it's on GLK where the change shouldn't have an effect. > > == Summary == > > CI Bug Log - changes from CI_DRM_11972_full -> Patchwork_107059v1_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_107059v1_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_107059v1_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (12 -> 12) > -- > > No changes in participating hosts > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_107059v1_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_flip@2x-absolute-wf_vblank-interruptible: > - shard-glk: NOTRUN -> [TIMEOUT][1] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-glk7 > /igt@kms_flip@2x-absolute-wf_vblank-interruptible.html > > * igt@perf@enable-disable: > - shard-glk: [PASS][2] -> [TIMEOUT][3] +1 similar issue >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11972/shard-glk9/igt@p...@enable-disable.html >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-glk7 > /igt@p...@enable-disable.html > > > Warnings > > * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-fullscreen: > - shard-glk: [SKIP][4] ([fdo#109271]) -> [TIMEOUT][5] +3 similar > issues >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11972/shard-glk9/igt@kms_frontbuffer_track...@psr-2p-scndscrn-spr-indfb-fullscreen.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-glk7 > /igt@kms_frontbuffer_track...@psr-2p-scndscrn-spr-indfb-fullscreen.htm > l > > > Known issues > > > Here are the changes found in Patchwork_107059v1_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@drm_mm@all: > - shard-kbl: NOTRUN -> [SKIP][6] ([fdo#109271]) +157 similar > issues >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-kbl7 > /igt@drm...@all.html > > * igt@gem_exec_balancer@parallel-keep-submit-fence: > - shard-iclb: [PASS][7] -> [SKIP][8] ([i915#4525]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11972/shard-iclb1/igt@gem_exec_balan...@parallel-keep-submit-fence.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-iclb > 5/igt@gem_exec_balan...@parallel-keep-submit-fence.html > > * igt@gem_exec_balancer@parallel-ordering: > - shard-kbl: NOTRUN -> [FAIL][9] ([i915#6117]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-kbl1 > /igt@gem_exec_balan...@parallel-ordering.html > > * igt@gem_exec_fair@basic-none@vcs0: > - shard-kbl: NOTRUN -> [FAIL][10] ([i915#2842]) +1 similar issue >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-kbl7 > /igt@gem_exec_fair@basic-n...@vcs0.html > > * igt@gem_exec_fair@basic-pace@rcs0: > - shard-kbl: [PASS][11] -> [FAIL][12] ([i915#2842]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11972/shard-kbl4/igt@gem_exec_fair@basic-p...@rcs0.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107059v1/shard-kbl7 > /igt@gem_exec_fair@basic-p...@rcs0.html > > * igt@gem_exec_fair@basic-throttle@rcs0: > - shard-iclb: [PASS][13] -> [FAIL][14] ([i915#2849]) >[13]: > https://intel-gfx-ci.01.org/tr
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3)
I have never done that. Author probably should have access to that. If I remember correctly, there should be a re-run button which I not able to see at the moment. Lakshmi. From: Shankar, Uma Sent: Thursday, July 28, 2022 10:50 PM To: Kurmi, Suresh Kumar ; Vudum, Lakshminarayana ; Lee, Shawn C ; intel-gfx@lists.freedesktop.org; Naramasetti, LaxminarayanaX Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) Hi Lakshmi, Can you trigger a re-run just to confirm as recommended by Suresh. Regards, Uma Shankar From: Kurmi, Suresh Kumar mailto:suresh.kumar.ku...@intel.com>> Sent: Friday, July 29, 2022 9:29 AM To: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>>; Lee, Shawn C mailto:shawn.c@intel.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>; Naramasetti, LaxminarayanaX mailto:laxminarayanax.naramase...@intel.com>> Cc: Shankar, Uma mailto:uma.shan...@intel.com>> Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) IGT_6598 is very old, we should trigger the re-run with the latest CI IGT version since ADL-M and RKL has been very stable BAT machine. -Suresh From: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Sent: Thursday, July 28, 2022 9:08 PM To: Lee, Shawn C mailto:shawn.c@intel.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>; Kurmi, Suresh Kumar mailto:suresh.kumar.ku...@intel.com>>; Naramasetti, LaxminarayanaX mailto:laxminarayanax.naramase...@intel.com>> Cc: Shankar, Uma mailto:uma.shan...@intel.com>> Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) From: Vudum, Lakshminarayana Sent: Thursday, July 28, 2022 8:36 AM To: 20220722070343.10654-1-shawn.c@intel.com<mailto:20220722070343.10654-1-shawn.c@intel.com>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>; Kurmi, Suresh Kumar mailto:suresh.kumar.ku...@intel.com>>; Naramasetti, LaxminarayanaX mailto:laxminarayanax.naramase...@intel.com>> Cc: Shankar, Uma mailto:uma.shan...@intel.com>> Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) Shawn, I see from our CI that we haven’t seen FIFO underruns lately on ADL-M and RKL. I see your series is using IGT_6598 and CI is using IGT_6603. Not sure, how old is the one used in the series and how much it makes difference. @Kurmi, Suresh Kumar<mailto:suresh.kumar.ku...@intel.com>/@Naramasetti, LaxminarayanaX<mailto:laxminarayanax.naramase...@intel.com> How do you see this issue? Should I file a new issue and re-report? Thanks, Lakshmi. From: Lee, Shawn C mailto:shawn.c@intel.com>> Sent: Thursday, July 28, 2022 8:10 AM To: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org> Cc: Shankar, Uma mailto:uma.shan...@intel.com>>; Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) Hi Lakshmi, Below issues are not related to the patch. Re-run these test cases with this patch and get pass result on my local machine. Best regards, Shawn From: Patchwork mailto:patchw...@emeril.freedesktop.org>> Sent: Wednesday, July 27, 2022 4:54 PM To: Lee, Shawn C mailto:shawn.c@intel.com>> Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org> Subject: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3) Patch Details Series: drm/i915: clear plane color ctl setting when turn full plane off (rev3) URL: https://patchwork.freedesktop.org/series/106292/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/index.html CI Bug Log - changes from CI_DRM_11946 -> Patchwork_106292v3 Summary FAILURE Serious unknown changes coming with Patchwork_106292v3 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_106292v3, please notify your bug team 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_106292v3/index.html Participating hosts (38 -> 37) Additional (2): fi-hsw-4770 bat-jsl-1 Missing (3): fi-rkl-11600 fi-bdw-samus bat-dg1-5 Possible new issues Here are the unknown changes that may have been introduced in Patchwork_106292v3: IGT changes Possible regressions * igt@kms_cursor_legacy@basic-flip-after-cursor@atomic-transitions: * fi-adl-ddr5: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-adl-dd
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3)
From: Vudum, Lakshminarayana
Sent: Thursday, July 28, 2022 8:36 AM
To: 20220722070343.10654-1-shawn.c@intel.com;
intel-gfx@lists.freedesktop.org; Kurmi, Suresh Kumar
; Naramasetti, LaxminarayanaX
Cc: Shankar, Uma
Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting
when turn full plane off (rev3)
Shawn,
I see from our CI that we haven’t seen FIFO underruns lately on ADL-M and RKL.
I see your series is using IGT_6598 and CI is using IGT_6603. Not sure, how old
is the one used in the series and how much it makes difference.
@Kurmi, Suresh Kumar<mailto:suresh.kumar.ku...@intel.com>/@Naramasetti,
LaxminarayanaX<mailto:laxminarayanax.naramase...@intel.com> How do you see this
issue? Should I file a new issue and re-report?
Thanks,
Lakshmi.
From: Lee, Shawn C mailto:shawn.c@intel.com>>
Sent: Thursday, July 28, 2022 8:10 AM
To: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Cc: Shankar, Uma mailto:uma.shan...@intel.com>>; Vudum,
Lakshminarayana
mailto:lakshminarayana.vu...@intel.com>>
Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting
when turn full plane off (rev3)
Hi Lakshmi,
Below issues are not related to the patch. Re-run these test cases with this
patch and get pass result on my local machine.
Best regards,
Shawn
From: Patchwork
mailto:patchw...@emeril.freedesktop.org>>
Sent: Wednesday, July 27, 2022 4:54 PM
To: Lee, Shawn C mailto:shawn.c@intel.com>>
Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Subject: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when
turn full plane off (rev3)
Patch Details
Series:
drm/i915: clear plane color ctl setting when turn full plane off (rev3)
URL:
https://patchwork.freedesktop.org/series/106292/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/index.html
CI Bug Log - changes from CI_DRM_11946 -> Patchwork_106292v3
Summary
FAILURE
Serious unknown changes coming with Patchwork_106292v3 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106292v3, please notify your bug team 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_106292v3/index.html
Participating hosts (38 -> 37)
Additional (2): fi-hsw-4770 bat-jsl-1
Missing (3): fi-rkl-11600 fi-bdw-samus bat-dg1-5
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_106292v3:
IGT changes
Possible regressions
* igt@kms_cursor_legacy@basic-flip-after-cursor@atomic-transitions:
* fi-adl-ddr5:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-adl-ddr5/igt@kms_cursor_legacy@basic-flip-after-cur...@atomic-transitions.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-adl-ddr5/igt@kms_cursor_legacy@basic-flip-after-cur...@atomic-transitions.html>
+4 similar issues
*
igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions-varying-size:
* fi-rkl-guc:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-rkl-guc/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-rkl-guc/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+3 similar issues
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions:
* {bat-rplp-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/bat-rplp-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/bat-rplp-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions.html>
+3 similar issues
*
igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions-varying-size:
* {bat-rpls-2}: NOTRUN ->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/bat-rpls-2/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+15 similar issues
* {fi-jsl-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-jsl-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-jsl-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+4 similar issues
* {bat-rpls-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/bat-rpls-1/igt@kms_c
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when turn full plane off (rev3)
Shawn,
I see from our CI that we haven’t seen FIFO underruns lately on ADL-M and RKL.
I see your series is using IGT_6598 and CI is using IGT_6603. Not sure, how old
is the one used in the series and how much it makes difference.
@Kurmi, Suresh Kumar<mailto:suresh.kumar.ku...@intel.com>/@Naramasetti,
LaxminarayanaX<mailto:laxminarayanax.naramase...@intel.com> How do you see this
issue? Should I file a new issue and re-report?
Thanks,
Lakshmi.
From: Lee, Shawn C
Sent: Thursday, July 28, 2022 8:10 AM
To: intel-gfx@lists.freedesktop.org
Cc: Shankar, Uma ; Vudum, Lakshminarayana
Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting
when turn full plane off (rev3)
Hi Lakshmi,
Below issues are not related to the patch. Re-run these test cases with this
patch and get pass result on my local machine.
Best regards,
Shawn
From: Patchwork
mailto:patchw...@emeril.freedesktop.org>>
Sent: Wednesday, July 27, 2022 4:54 PM
To: Lee, Shawn C mailto:shawn.c@intel.com>>
Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Subject: ✗ Fi.CI.BAT: failure for drm/i915: clear plane color ctl setting when
turn full plane off (rev3)
Patch Details
Series:
drm/i915: clear plane color ctl setting when turn full plane off (rev3)
URL:
https://patchwork.freedesktop.org/series/106292/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/index.html
CI Bug Log - changes from CI_DRM_11946 -> Patchwork_106292v3
Summary
FAILURE
Serious unknown changes coming with Patchwork_106292v3 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106292v3, please notify your bug team 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_106292v3/index.html
Participating hosts (38 -> 37)
Additional (2): fi-hsw-4770 bat-jsl-1
Missing (3): fi-rkl-11600 fi-bdw-samus bat-dg1-5
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_106292v3:
IGT changes
Possible regressions
* igt@kms_cursor_legacy@basic-flip-after-cursor@atomic-transitions:
* fi-adl-ddr5:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-adl-ddr5/igt@kms_cursor_legacy@basic-flip-after-cur...@atomic-transitions.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-adl-ddr5/igt@kms_cursor_legacy@basic-flip-after-cur...@atomic-transitions.html>
+4 similar issues
*
igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions-varying-size:
* fi-rkl-guc:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-rkl-guc/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-rkl-guc/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+3 similar issues
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions:
* {bat-rplp-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/bat-rplp-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/bat-rplp-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions.html>
+3 similar issues
*
igt@kms_cursor_legacy@basic-flip-before-cursor@atomic-transitions-varying-size:
* {bat-rpls-2}: NOTRUN ->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/bat-rpls-2/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+15 similar issues
* {fi-jsl-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-jsl-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/fi-jsl-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+4 similar issues
* {bat-rpls-1}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/bat-rpls-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106292v3/bat-rpls-1/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
+5 similar issues
* {fi-ehl-2}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/fi-ehl-2/igt@kms_cursor_legacy@basic-flip-before-cur...@atomic-transitions-varying-size.html>
->
DMESG-WARN<https://intel-gfx-ci.01.o
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order
Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6460 and re-reported. But shards re-reporting is not working at the moment? FYI @Sarvela, Tomi P Lakshmi. -Original Message- From: Deak, Imre Sent: Monday, July 18, 2022 5:21 AM To: intel-gfx@lists.freedesktop.org; Nautiyal, Ankit K ; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order On Sat, Jun 18, 2022 at 12:50:26AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order > URL : https://patchwork.freedesktop.org/series/105290/ > State : failure Thanks for the review, patch pushed to drm-intel-next. The failure is unrelated, see below. > == Summary == > > CI Bug Log - changes from CI_DRM_11775_full -> Patchwork_105290v1_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_105290v1_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_105290v1_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 -> 10) > -- > > Missing(3): shard-rkl shard-dg1 shard-tglu > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_105290v1_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_atomic_transition@modeset-transition-nonblocking@1x-outputs: > - shard-tglb: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-tglb5/igt@kms_atomic_transition@modeset-transition-nonblock...@1x-outputs.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105290v1/shard-tglb > 3/igt@kms_atomic_transition@modeset-transition-nonblocking@1x-outputs. > html There is no HDMI output modesetted on the above machine, so the issue is unrelated. > Known issues > > > Here are the changes found in Patchwork_105290v1_full that come from known > issues: > > ### CI changes ### > > Issues hit > > * boot: > - shard-apl: ([PASS][3], [PASS][4], [PASS][5], [PASS][6], > [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], > [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], > [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], > [PASS][25], [PASS][26], [PASS][27]) -> ([PASS][28], [PASS][29], [PASS][30], > [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], > [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], > [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], > [PASS][49], [PASS][50], [FAIL][51], [PASS][52]) ([i915#4386]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl8/boot.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl8/boot.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl8/boot.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl8/boot.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl7/boot.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl7/boot.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl7/boot.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl7/boot.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl6/boot.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl6/boot.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl6/boot.html >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl4/boot.html >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl4/boot.html >[16]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl4/boot.html >[17]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl3/boot.html >[18]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl3/boot.html >[19]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl3/boot.html >[20]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11775/shard-apl3/boot.html >
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Correct ss -> steering calculation for pre-Xe_HP platforms
We are tracking igt@i915_selftest@live@hangcheck failures with no logs here
https://gitlab.freedesktop.org/drm/intel/-/issues/6172
igt@i915_selftest@live@hangcheck - incomplete - No warnings/errors
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Wednesday, July 13, 2022 9:26 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Correct ss -> steering
calculation for pre-Xe_HP platforms
On Wed, Jul 13, 2022 at 03:50:35AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Correct ss -> steering calculation for pre-Xe_HP platforms
> URL : https://patchwork.freedesktop.org/series/106269/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11877_full -> Patchwork_106269v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_106269v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_106269v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_106269v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@live@hangcheck:
> - shard-skl: NOTRUN -> [INCOMPLETE][1]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106269v1/shard-skl9/igt@i915_selftest@l...@hangcheck.html
Random incomplete (logs cut off abruptly with no errors reported). Does
not appear to be related to this patch.
Patch applied to drm-intel-gt-next. Thanks Lucas for the review.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@drm_buddy@all:
> - {shard-dg1}:NOTRUN -> [SKIP][2] +4 similar issues
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106269v1/shard-dg1-15/igt@drm_bu...@all.html
>
> * igt@kms_setmode@clone-exclusive-crtc:
> - {shard-dg1}:NOTRUN -> [INCOMPLETE][3]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106269v1/shard-dg1-16/igt@kms_setm...@clone-exclusive-crtc.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_106269v1_full that come from known
> issues:
>
> ### CI changes ###
>
> Issues hit
>
> * boot:
> - shard-skl: ([PASS][4], [PASS][5], [PASS][6], [PASS][7],
> [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13],
> [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19],
> [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24]) -> ([PASS][25],
> [PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31],
> [PASS][32], [PASS][33], [PASS][34], [FAIL][35], [PASS][36], [PASS][37],
> [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43],
> [PASS][44]) ([i915#5032])
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl9/boot.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl9/boot.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl7/boot.html
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl7/boot.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl6/boot.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl6/boot.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl5/boot.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl5/boot.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl4/boot.html
>[13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl4/boot.html
>[14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl4/boot.html
>[15]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl3/boot.html
>[16]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl3/boot.html
>[17]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11877/shard-skl2/boot.html
>[18]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DR
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915/dg2: Add Wa_15010599737
Re-reproted.
-Original Message-
From: Roper, Matthew D
Sent: Tuesday, July 12, 2022 8:55 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915/dg2:
Add Wa_15010599737
On Sat, Jul 09, 2022 at 07:41:45AM +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915/dg2: Add Wa_15010599737
> URL : https://patchwork.freedesktop.org/series/106130/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11862_full -> Patchwork_106130v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_106130v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_106130v1_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (10 -> 13)
> --
>
> Additional (3): shard-rkl shard-dg1 shard-tglu
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_106130v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-indfb-fliptrack-mmap-gtt:
> - shard-tglb: [PASS][1] -> [FAIL][2] +2 similar issues
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb7/igt@kms_frontbuffer_track...@fbcpsr-1p-indfb-fliptrack-mmap-gtt.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-tglb3/igt@kms_frontbuffer_track...@fbcpsr-1p-indfb-fliptrack-mmap-gtt.html
This is an expected regression in functionality due to the new
restrictions imposed by the workaround: the test now fails because
FBC is turned off whenever PSR1 is active. However that's exactly
what the workaround asks us to do (in order to avoid incorrect hardware
behavior).
>
> * igt@kms_invalid_mode@clock-too-high@edp-1-pipe-d:
> - shard-tglb: NOTRUN -> [SKIP][3] +3 similar issues
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-tglb1/igt@kms_invalid_mode@clock-too-h...@edp-1-pipe-d.html
https://gitlab.freedesktop.org/drm/intel/-/issues/6403
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-mmap-wc:
> - {shard-rkl}:NOTRUN -> [FAIL][4] +7 similar issues
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-rkl-6/igt@kms_frontbuffer_track...@fbcpsr-1p-primscrn-spr-indfb-draw-mmap-wc.html
>
> * igt@kms_invalid_mode@zero-vdisplay@hdmi-a-1-pipe-a:
> - {shard-dg1}:NOTRUN -> [WARN][5]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-dg1-19/igt@kms_invalid_mode@zero-vdisp...@hdmi-a-1-pipe-a.html
>
> * {igt@kms_rmfb@rmfb-ioctl@pipe-d-hdmi-a-1}:
> - {shard-dg1}:NOTRUN -> [FAIL][6] +3 similar issues
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-dg1-19/igt@kms_rmfb@rmfb-io...@pipe-d-hdmi-a-1.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_106130v1_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_create@create-massive:
> - shard-apl: NOTRUN -> [DMESG-WARN][7] ([i915#4991])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-apl3/igt@gem_cre...@create-massive.html
>
> * igt@gem_ctx_persistence@engines-hostile-preempt:
> - shard-snb: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#1099]) +1
> similar issue
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-snb4/igt@gem_ctx_persiste...@engines-hostile-preempt.html
>
> * igt@gem_ctx_persistence@hostile:
> - shard-tglb: NOTRUN -> [FAIL][9] ([i915#2410])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-tglb1/igt@gem_ctx_persiste...@hostile.html
>
> * igt@gem_exec_balancer@parallel-balancer:
> - shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271]) +26 similar
> issues
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106130v1/shard-snb4/igt@gem_exec_balan...@parallel-balancer.html
>
> * igt@gem_exec_fair@basic-non
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Introduce Meteorlake
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/6169
Few tests - incomplete - pstore logs, Kernel panic - not syncing: Software
Watchdog Timer expired, RIP: 0010:cpuidle_enter_state
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Friday, July 8, 2022 1:34 PM
To: intel-gfx@lists.freedesktop.org
Cc: Sripada, Radhakrishna ; Vudum,
Lakshminarayana ; Vivi, Rodrigo
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Introduce Meteorlake
On Fri, Jul 08, 2022 at 04:38:48PM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915: Introduce Meteorlake
> URL : https://patchwork.freedesktop.org/series/106075/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11859_full -> Patchwork_106075v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_106075v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_106075v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_106075v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_exec_schedule@wide@vcs1:
> - shard-kbl: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-kbl4/igt@gem_exec_schedule@w...@vcs1.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106075v1/shard-kbl1/igt@gem_exec_schedule@w...@vcs1.html
Test actually finished executing, but then there were some NVME errors,
followed by
<2>[ 334.527621] softdog: Initiating panic
<0>[ 334.529807] Kernel panic - not syncing: Software Watchdog Timer expired
This looks like general system instability, likely not related to
graphics at all.
Series applied to drm-intel-gt-next (as suggested by Rodrigo, since this
will allow the IS_METEORLAKE definitions to be cross-pollinated across
both drm-intel branches most easily).
Thanks for the patches.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_pm_rc6_residency@rc6-idle@vcs0:
> - {shard-rkl}:NOTRUN -> [WARN][3]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106075v1/shard-rkl-5/igt@i915_pm_rc6_residency@rc6-i...@vcs0.html
>
> * igt@kms_cursor_legacy@cursor-vs-flip@atomic:
> - {shard-dg1}:[PASS][4] -> [FAIL][5] +4 similar issues
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-dg1-12/igt@kms_cursor_legacy@cursor-vs-f...@atomic.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106075v1/shard-dg1-15/igt@kms_cursor_legacy@cursor-vs-f...@atomic.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_106075v1_full that come from known
> issues:
>
> ### CI changes ###
>
> Possible fixes
>
> * boot:
> - shard-skl: ([PASS][6], [PASS][7], [PASS][8], [PASS][9],
> [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15],
> [PASS][16], [FAIL][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21],
> [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27],
> [PASS][28], [PASS][29], [PASS][30]) ([i915#5032]) -> ([PASS][31], [PASS][32],
> [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38],
> [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44],
> [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50],
> [PASS][51], [PASS][52])
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl10/boot.html
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl10/boot.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl10/boot.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl1/boot.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl1/boot.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl3/boot.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11859/shard-skl3/boot.html
>[13]:
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
Filed a new issue for the mismatch.
https://gitlab.freedesktop.org/drm/intel/-/issues/6400
igt@kms_pipe_crc_basic@.* - fail - Failed assertion: !mismatch ||
igt_skip_crc_compare
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Friday, July 8, 2022 9:35 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/gt: Add general DSS steering
iterator to intel_gt_mcr (rev2)
On Sat, Jul 02, 2022 at 06:25:09PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
> URL : https://patchwork.freedesktop.org/series/105883/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11842_full -> Patchwork_105883v2_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_105883v2_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_105883v2_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (10 -> 13)
> --
>
> Additional (3): shard-rkl shard-dg1 shard-tglu
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_105883v2_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> *
> igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-downscaling@pipe-a-valid-mode:
> - shard-iclb: NOTRUN -> [SKIP][1] +3 similar issues
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-downscal...@pipe-a-valid-mode.html
Seems to be new tests that match
https://gitlab.freedesktop.org/drm/intel/-/issues/2672 .
New tests were likely introduced by
commit 01f75333df0d27768ef987653ab49c3a1223ce3d
Author: Swati Sharma
AuthorDate: Thu Jun 30 13:15:11 2022 +0300
Commit: Juha-Pekka Heikkila
CommitDate: Fri Jul 1 12:41:09 2022 +0300
tests/i915/kms_flip_scaled_crc: Add new tests covering modifiers and
pixel-formats
>
> * igt@kms_pipe_crc_basic@nonblocking-crc-frame-sequence@pipe-b-hdmi-a-2:
> - shard-glk: [PASS][2] -> [FAIL][3]
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11842/shard-glk7/igt@kms_pipe_crc_basic@nonblocking-crc-frame-seque...@pipe-b-hdmi-a-2.html
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-glk1/igt@kms_pipe_crc_basic@nonblocking-crc-frame-seque...@pipe-b-hdmi-a-2.html
CRC mismatch. Display CRCs would not be impacted by this patch which
just adds a new GT loop interface
Patch applied to drm-intel-gt-next. Thanks Matt Atwood for the review.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_capture@pi@rcs0:
> - {shard-dg1}:NOTRUN -> [INCOMPLETE][4]
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-dg1-15/igt@gem_exec_capture@p...@rcs0.html
>
> *
> igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-downscaling@pipe-a-valid-mode:
> - {shard-tglu}: NOTRUN -> [SKIP][5] +14 similar issues
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-tglu-6/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-downscal...@pipe-a-valid-mode.html
>
> *
> igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-upscaling@pipe-a-valid-mode:
> - {shard-dg1}:NOTRUN -> [SKIP][6] +13 similar issues
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-dg1-12/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-upscal...@pipe-a-valid-mode.html
>
> * igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling:
> - {shard-rkl}:NOTRUN -> [SKIP][7] +31 similar issues
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-rkl-5/igt@kms_flip_scaled_...@flip-64bpp-linear-to-16bpp-linear-downscaling.html
>
> *
> {igt@kms_flip_scaled_crc@flip-64bpp-linear-to-32bpp-linear-downscaling@pipe-a-default-mode}:
> - shard-iclb: NOTRUN -> [SKIP][8] +2 similar issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105883v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-32bpp-linear-downscal...@pipe-a-default-mode.ht
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Implement w/a 16016694945
They both are known issues. Re-reported.
-Original Message-
From: Roper, Matthew D
Sent: Friday, July 1, 2022 8:44 AM
To: intel-gfx@lists.freedesktop.org
Cc: Sousa, Gustavo ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Implement w/a
16016694945
On Fri, Jul 01, 2022 at 12:52:21PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/pvc: Implement w/a 16016694945
> URL : https://patchwork.freedesktop.org/series/105837/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11835_full -> Patchwork_105837v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_105837v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_105837v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_105837v1_full:
>
> ### IGT changes ###
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_create@create-ext-cpu-access-big:
> - {shard-rkl}:NOTRUN -> [SKIP][1]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-rkl-5/igt@gem_cre...@create-ext-cpu-access-big.html
>
> * igt@i915_query@query-regions-unallocated:
> - {shard-dg1}:NOTRUN -> [SKIP][2] +2 similar issues
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-dg1-16/igt@i915_qu...@query-regions-unallocated.html
These both look like new tests that were just added to exercise small
BAR support; I believe the skips were expected until the corresponding
kernel changes from Matt Auld landed (which just happened this morning,
probably after this series was tested). Not related to Gustavo's patch
here.
>
>
> ### Piglit changes ###
>
> Possible regressions
>
> * spec@arb_gpu_shader5@texturegatheroffset@vs-rgba-3-unorm-2drect-const:
> - pig-glk-j5005: NOTRUN -> [CRASH][3] +1 similar issue
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/pig-glk-j5005/spec@arb_gpu_shader5@texturegatheroff...@vs-rgba-3-unorm-2drect-const.html
>
> * spec@ext_texture_snorm@fbo-colormask-formats:
> - pig-skl-6260u: NOTRUN -> [INCOMPLETE][4]
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/pig-skl-6260u/spec@ext_texture_sn...@fbo-colormask-formats.html
The PVC workaround wouldn't have impacted execution on old gen9
platforms like GLK and SKL. Not related to Gustavo's patch.
Applied to drm-intel-gt-next. Thanks for the patch.
Matt
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_105837v1_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_ctx_persistence@hang:
> - shard-skl: NOTRUN -> [SKIP][5] ([fdo#109271]) +116 similar
> issues
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-skl6/igt@gem_ctx_persiste...@hang.html
>
> * igt@gem_eio@unwedge-stress:
> - shard-tglb: [PASS][6] -> [FAIL][7] ([i915#5784])
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11835/shard-tglb7/igt@gem_...@unwedge-stress.html
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-tglb5/igt@gem_...@unwedge-stress.html
>
> * igt@gem_exec_balancer@parallel-bb-first:
> - shard-iclb: [PASS][8] -> [SKIP][9] ([i915#4525]) +1 similar
> issue
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11835/shard-iclb2/igt@gem_exec_balan...@parallel-bb-first.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-iclb3/igt@gem_exec_balan...@parallel-bb-first.html
>
> * igt@gem_exec_fair@basic-none@vcs0:
> - shard-apl: [PASS][10] -> [FAIL][11] ([i915#2842]) +1 similar
> issue
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11835/shard-apl8/igt@gem_exec_fair@basic-n...@vcs0.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105837v1/shard-apl7/igt@gem_exec_fair@basic-n...@vcs0.html
>
> * igt@gem_exec_fair@
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,v4,01/13] drm/doc: add rfc section for small BAR uapi
Re-reported. Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6326 igt@i915_query@query-regions-garbage-items - fail - Failed assertion: info.rsvd1[j] == 0 Lakshmi. -Original Message- From: Auld, Matthew Sent: Thursday, June 30, 2022 5:39 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [CI,v4,01/13] drm/doc: add rfc section for small BAR uapi On 30/06/2022 10:42, Patchwork wrote: > *Patch Details* > *Series:* series starting with [CI,v4,01/13] drm/doc: add rfc section > for small BAR uapi > *URL:*https://patchwork.freedesktop.org/series/105787/ > <https://patchwork.freedesktop.org/series/105787/> > *State:* failure > *Details:* > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/index.html > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/index.html> > > > CI Bug Log - changes from CI_DRM_11825_full -> Patchwork_105787v1_full > > > Summary > > *FAILURE* > > Serious unknown changes coming with Patchwork_105787v1_full absolutely > need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_105787v1_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 -> 13) > > No changes in participating hosts > > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_105787v1_full: > > > IGT changes > > > Possible regressions > > * > > igt@i915_query@query-regions-garbage-items: > > o > > shard-apl: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-apl2/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-apl7/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-tglb: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-tglb2/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-tglb7/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-glk: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-glk3/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-glk8/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-iclb: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-iclb4/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-iclb2/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-kbl: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-kbl1/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-kbl6/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-snb: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-snb5/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-snb5/igt@i915_qu...@query-regions-garbage-items.html> > > o > > shard-skl: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11825/shard-skl1/igt@i915_qu...@query-regions-garbage-items.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-skl7/igt@i915_qu...@query-regions-garbage-items.html> > > * > > igt@kms_cursor_legacy@cursor-vs-flip@atomic: > > o shard-skl: NOTRUN -> INCOMPLETE > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105787v1/shard-skl1/igt@kms_cursor_legacy@cursor-vs-f...@atomic.html> This one looks unrelated. The other failures are expected/normal until the IGT series is merged (plan is merge that first so we don't see these failures): https://patchwork.freedesktop.org/series/105792/ > > > Suppressed > > The following results come from unt
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/2] iosys-map: Add per-word read (rev2)
Created new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6328 igt@kms_cursor_legacy@flip-vs-cursor.* - fail - Timed out: Stuck page flip Lakshmi. -Original Message- From: De Marchi, Lucas Sent: Wednesday, June 29, 2022 5:23 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [CI,1/2] iosys-map: Add per-word read (rev2) On Wed, Jun 29, 2022 at 09:20:46PM +, Patchwork wrote: >== Series Details == > >Series: series starting with [CI,1/2] iosys-map: Add per-word read (rev2) >URL : https://patchwork.freedesktop.org/series/105746/ >State : failure > >== Summary == > >CI Bug Log - changes from CI_DRM_11823_full -> Patchwork_105746v2_full > > >Summary >--- > > **FAILURE** > > Serious unknown changes coming with Patchwork_105746v2_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_105746v2_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 -> 13) >-- > > No changes in participating hosts > >Possible new issues >--- > > Here are the unknown changes that may have been introduced in > Patchwork_105746v2_full: > >### IGT changes ### > > Possible regressions > > * igt@kms_cursor_legacy@cursor-vs-flip@atomic-transitions-varying-size: >- shard-iclb: [PASS][1] -> [FAIL][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-iclb1/igt@kms_cursor_legacy@cursor-vs-f...@atomic-transitions-varying-size.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v2/shard-iclb7/igt@kms_cursor_legacy@cursor-vs-f...@atomic-transitions-varying-size.html > > * igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions: >- shard-tglb: [PASS][3] -> [FAIL][4] +1 similar issue > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-tglb5/igt@kms_cursor_legacy@flip-vs-cur...@atomic-transitions.html > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v2/shard-tglb1/igt@kms_cursor_legacy@flip-vs-cur...@atomic-transitions.html none of these are related with the iosys-map changes. Outside of guc, iosys_map is currently only used in i915 by i915_gem_prime_export which is not exercised by these display tests. Lucas De Marchi > > > >### Piglit changes ### > > Possible regressions > > * spec@!opengl 1.1@teximage-colors gl_rgba32f: >- pig-skl-6260u: NOTRUN -> [INCOMPLETE][5] > [5]: None > > * spec@glsl-1.10@execution@variable-indexing@vs-varying-mat2-rd: >- pig-glk-j5005: NOTRUN -> [INCOMPLETE][6] > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v2/pig-glk-j5005/spec@glsl-1.10@execution@variable-index...@vs-varying-mat2-rd.html > > >Known issues > > > Here are the changes found in Patchwork_105746v2_full that come from known > issues: > >### CI changes ### > > Possible fixes > > * boot: >- shard-glk: ([PASS][7], [PASS][8], [PASS][9], [PASS][10], > [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], > [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21], [PASS][22], > [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [FAIL][28], > [PASS][29], [PASS][30], [PASS][31]) ([i915#4392]) -> ([PASS][32], [PASS][33], > [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], > [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], > [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], > [PASS][52], [PASS][53], [PASS][54], [PASS][55], [PASS][56]) > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk5/boot.html > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk5/boot.html > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk6/boot.html > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk5/boot.html > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk6/boot.html > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk6/boot.html > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk7/boot.html > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk7/boot.html > [15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11823/shard-glk3/boot.html
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [CI,1/2] iosys-map: Add per-word read
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/6310
All tests - general protection fault, probably for non-canonical address
0x6b6b6b6b6b6b7c6b
Since we have clean BAT results from Rev 2, I haven’t re-reported.
Lakshmi.
From: Lucas De Marchi
Sent: Tuesday, June 28, 2022 5:09 PM
To: Intel Graphics
Cc: De Marchi, Lucas ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [CI,1/2]
iosys-map: Add per-word read
+Lakshmi
Can't see how these would be related. Searching recent failure I found this
very similar one:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11814/shard-glk7/pstore24-1656384153_Oops_1.txt
Lucas De Marchi
On Tue, Jun 28, 2022 at 3:49 PM Patchwork
mailto:patchw...@emeril.freedesktop.org>>
wrote:
Patch Details
Series:
series starting with [CI,1/2] iosys-map: Add per-word read
URL:
https://patchwork.freedesktop.org/series/105746/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/index.html
CI Bug Log - changes from CI_DRM_11820 -> Patchwork_105746v1
Summary
FAILURE
Serious unknown changes coming with Patchwork_105746v1 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_105746v1, please notify your bug team 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_105746v1/index.html
Participating hosts (38 -> 37)
Missing (1): bat-adlp-4
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_105746v1:
IGT changes
Possible regressions
* igt@gem_exec_parallel@engines@fds:
* fi-bsw-kefka:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11820/fi-bsw-kefka/igt@gem_exec_parallel@engi...@fds.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-bsw-kefka/igt@gem_exec_parallel@engi...@fds.html>
* fi-cfl-8109u:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11820/fi-cfl-8109u/igt@gem_exec_parallel@engi...@fds.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-cfl-8109u/igt@gem_exec_parallel@engi...@fds.html>
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_selftest@live@gt_heartbeat:
* {bat-adln-1}: NOTRUN ->
DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/bat-adln-1/igt@i915_selftest@live@gt_heartbeat.html>
Known issues
Here are the changes found in Patchwork_105746v1 that come from known issues:
IGT changes
Issues hit
* igt@i915_selftest@live@hangcheck:
* fi-hsw-g3258:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11820/fi-hsw-g3258/igt@i915_selftest@l...@hangcheck.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-hsw-g3258/igt@i915_selftest@l...@hangcheck.html>
(i915#4785<https://gitlab.freedesktop.org/drm/intel/issues/4785>)
* igt@i915_selftest@live@late_gt_pm:
* fi-bsw-nick:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11820/fi-bsw-nick/igt@i915_selftest@live@late_gt_pm.html>
->
DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-bsw-nick/igt@i915_selftest@live@late_gt_pm.html>
(i915#3428<https://gitlab.freedesktop.org/drm/intel/issues/3428>)
* igt@kms_chamelium@common-hpd-after-suspend:
* fi-pnv-d510: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-pnv-d510/igt@kms_chamel...@common-hpd-after-suspend.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>)
* igt@runner@aborted:
* fi-cfl-8109u: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-cfl-8109u/igt@run...@aborted.html>
(i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
* fi-bsw-nick: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-bsw-nick/igt@run...@aborted.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
i915#3428<https://gitlab.freedesktop.org/drm/intel/issues/3428> /
i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
* fi-hsw-g3258: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-hsw-g3258/igt@run...@aborted.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> /
i915#6246<https://gitlab.freedesktop.org/drm/intel/issues/6246>)
* fi-bsw-kefka: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105746v1/fi-bsw-kefka/igt@run...@aborted.html>
(i915#4312<https
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: tweak the ordering in cpu_write_needs_clflush
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/2346
igt@kms_cursor_legacy@flip-vs-cursor - fail - Failed assertion:
kmstest_get_vblank(display->drm_fd, pipe, 0) == vblank_start|Failed assertion:
kmstest_get_vblank(display->drm_fd, pipe, 0) <= vblank_start + 1
Thanks,
Lakshmi.
-Original Message-
From: Matthew Auld
Sent: Monday, June 27, 2022 5:04 AM
To: Intel Graphics Development ; Vudum,
Lakshminarayana
Cc: Auld, Matthew
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: tweak the ordering
in cpu_write_needs_clflush
On Mon, 27 Jun 2022 at 12:49, Patchwork
wrote:
>
> Patch Details
> Series:drm/i915: tweak the ordering in cpu_write_needs_clflush
> URL:https://patchwork.freedesktop.org/series/105503/
> State:failure
> Details:https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105503v1/in
> dex.html
>
> CI Bug Log - changes from CI_DRM_11795_full -> Patchwork_105503v1_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_105503v1_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_105503v1_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 -> 13)
>
> No changes in participating hosts
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_105503v1_full:
>
> IGT changes
>
> Possible regressions
>
> igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
>
> shard-skl: NOTRUN -> FAIL +1 similar issue
For sure unrelated. Patch only impacts discrete.
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> {igt@kms_cursor_crc@cursor-offscreen@pipe-d-hdmi-a-1-32x10}:
>
> {shard-dg1}: NOTRUN -> SKIP +15 similar issues
>
> igt@kms_cursor_crc@cursor-rapid-movement@pipe-b-edp-1-32x32:
>
> {shard-rkl}: NOTRUN -> SKIP +3 similar issues
>
> New tests
>
> New tests have been introduced between CI_DRM_11795_full and
> Patchwork_105503v1_full:
>
> New IGT tests (7)
>
> igt@kms_cursor_edge_walk@right-edge@pipe-a-hdmi-a-3-128x128:
>
> Statuses : 1 pass(s)
> Exec time: [3.23] s
>
> igt@kms_cursor_edge_walk@right-edge@pipe-a-hdmi-a-3-256x256:
>
> Statuses : 1 pass(s)
> Exec time: [3.23] s
>
> igt@kms_cursor_edge_walk@right-edge@pipe-a-hdmi-a-3-64x64:
>
> Statuses : 1 pass(s)
> Exec time: [3.30] s
>
> igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-a-hdmi-a-3:
>
> Statuses : 1 pass(s)
> Exec time: [0.56] s
>
> igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-b-hdmi-a-3:
>
> Statuses : 1 pass(s)
> Exec time: [0.46] s
>
> igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-c-hdmi-a-3:
>
> Statuses : 1 pass(s)
> Exec time: [0.46] s
>
> igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-hdmi-a-3:
>
> Statuses : 1 pass(s)
> Exec time: [0.46] s
>
> Known issues
>
> Here are the changes found in Patchwork_105503v1_full that come from known
> issues:
>
> IGT changes
>
> Issues hit
>
> igt@gem_ctx_persistence@hang:
>
> shard-skl: NOTRUN -> SKIP (fdo#109271) +230 similar issues
>
> igt@gem_exec_balancer@parallel-balancer:
>
> shard-iclb: PASS -> SKIP (i915#4525)
>
> igt@gem_exec_fair@basic-none-share@rcs0:
>
> shard-glk: PASS -> FAIL (i915#2842)
>
> igt@gem_exec_fair@basic-none@vcs1:
>
> shard-kbl: PASS -> FAIL (i915#2842) +2 similar issues
>
> igt@gem_exec_fair@basic-pace-solo@rcs0:
>
> shard-tglb: PASS -> FAIL (i915#2842)
>
> igt@gem_exec_suspend@basic-s3@smem:
>
> shard-skl: PASS -> INCOMPLETE (i915#4939)
>
> igt@gem_lmem_swapping@heavy-verify-multi:
>
> shard-apl: NOTRUN -> SKIP (fdo#109271 / i915#4613)
>
> shard-tglb: NOTRUN -> SKIP (i915#4613)
>
> igt@gem_lmem_swapping@smem-oom:
>
> shard-skl: NOTRUN -> SKIP (fdo#109271 / i915#4613) +2 similar issues
>
> igt@gem_lmem_swapping@verify-random:
>
> shard-kbl: NOTRUN -> SKIP (fdo#109271 / i915#4613)
>
> igt@gem_pread@exhaustion:
>
> shard-kbl: NOTRUN -> WARN (i915#2658)
>
> igt@gem_pxp@regular-baseline-src-copy-readible:
>
> shard-tglb: NOTRUN -> SKIP (i915#4270)
>
> igt@gem_softpin@evict-snoop-interruptible:
>
> shard-iclb: NOTRUN -> SKIP (fdo#109312)
>
> igt@gen7_exec_parse@chained-batch:
>
> shard-tglb: NOTRUN -> SKIP (fdo#109289)
>
> igt@gen9_exec_parse@allowed-all:
>
> shard-glk: PASS -> DMESG-WARN (i915#5566 / i91
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] drm/i915/display: Add smem fallback allocation for dpt (rev5)
Issue is related to #5726. Updated the filters. -Original Message- From: Juha-Pekka Heikkila Sent: Friday, June 17, 2022 4:36 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/3] drm/i915/display: Add smem fallback allocation for dpt (rev5) Hi Lakshmi, here would be another false positive from ci. My changes are not affecting this error with busyness on skl with igt@kms_flip@busy-flip@a-edp1 /Juha-Pekka On 17.6.2022 13.19, Patchwork wrote: > *Patch Details* > *Series:* series starting with [1/3] drm/i915/display: Add smem fallback > allocation for dpt (rev5) > *URL:*https://patchwork.freedesktop.org/series/104983/ > <https://patchwork.freedesktop.org/series/104983/> > *State:* failure > *Details:* > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104983v5/index.html > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104983v5/index.htm > l> > > > CI Bug Log - changes from CI_DRM_11772_full -> > Patchwork_104983v5_full > > > Summary > > *FAILURE* > > Serious unknown changes coming with Patchwork_104983v5_full absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_104983v5_full, please notify your bug team to > allow them to document this new failure mode, which will reduce false > positives in CI. > > > Participating hosts (10 -> 10) > > No changes in participating hosts > > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_104983v5_full: > > > IGT changes > > > Possible regressions > > * igt@kms_flip@busy-flip@a-edp1: > o shard-skl: PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-skl2/igt@kms_flip@busy-f...@a-edp1.html> > -> FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104983v5/shard-skl > 4/igt@kms_flip@busy-f...@a-edp1.html> > > > Known issues > > Here are the changes found in Patchwork_104983v5_full that come from > known issues: > > > CI changes > > > Issues hit > > * boot: > o shard-glk: (PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk9/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk9/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk8/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk8/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk8/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk7/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk7/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk6/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk6/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk6/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk5/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk5/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk5/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk4/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk4/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk4/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk3/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk3/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk3/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk2/boot.html>, > PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11772/shard-glk2/boo
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/dp/mst: Read the extended DPCD capabilities during system resume
Failure is related to https://gitlab.freedesktop.org/drm/intel/-/issues/3063
Lakshmi.
-Original Message-
From: Deak, Imre
Sent: Thursday, June 16, 2022 11:58 AM
To: intel-gfx@lists.freedesktop.org; Nikula, Jani ;
Lyude Paul ; Vudum, Lakshminarayana
Cc: dri-de...@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for drm/dp/mst: Read the extended DPCD
capabilities during system resume
On Wed, Jun 15, 2022 at 04:25:34AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/dp/mst: Read the extended DPCD capabilities during system resume
> URL : https://patchwork.freedesktop.org/series/105102/
> State : failure
Thanks for the reviews, pushed the patch to drm-misc-next also adding
Cc: stable.
The failure is unrelated, see below.
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11756_full -> Patchwork_105102v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_105102v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_105102v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_105102v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_eio@reset-stress:
> - shard-snb: [PASS][1] -> [TIMEOUT][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11756/shard-snb7/igt@gem_...@reset-stress.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105102v1/shard-snb2/igt@gem_...@reset-stress.html
<7> [109.948420] heartbeat vcs0 heartbeat {seqno:5:11771, prio:-2147483648} not
ticking
SNB doesn't support MST, so it's some unrelated issue.
> New tests
> -
>
> New tests have been introduced between CI_DRM_11756_full and
> Patchwork_105102v1_full:
>
> ### New IGT tests (5) ###
>
> * igt@kms_atomic_interruptible@legacy-setmode@hdmi-a-3-pipe-a:
> - Statuses : 1 pass(s)
> - Exec time: [6.14] s
>
> * igt@kms_plane_lowres@tiling-none@pipe-a-hdmi-a-3:
> - Statuses : 1 pass(s)
> - Exec time: [8.02] s
>
> * igt@kms_plane_lowres@tiling-none@pipe-b-hdmi-a-3:
> - Statuses : 1 pass(s)
> - Exec time: [7.91] s
>
> * igt@kms_plane_lowres@tiling-none@pipe-c-hdmi-a-3:
> - Statuses : 1 pass(s)
> - Exec time: [7.93] s
>
> * igt@kms_plane_lowres@tiling-none@pipe-d-hdmi-a-3:
> - Statuses : 1 pass(s)
> - Exec time: [7.94] s
>
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_105102v1_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_eio@in-flight-contexts-1us:
> - shard-apl: [PASS][3] -> [TIMEOUT][4] ([i915#3063])
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11756/shard-apl2/igt@gem_...@in-flight-contexts-1us.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105102v1/shard-apl2/igt@gem_...@in-flight-contexts-1us.html
>
> * igt@gem_exec_balancer@parallel-keep-in-fence:
> - shard-iclb: [PASS][5] -> [SKIP][6] ([i915#4525]) +2 similar
> issues
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11756/shard-iclb2/igt@gem_exec_balan...@parallel-keep-in-fence.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105102v1/shard-iclb5/igt@gem_exec_balan...@parallel-keep-in-fence.html
>
> * igt@gem_exec_capture@pi@vcs0:
> - shard-iclb: [PASS][7] -> [INCOMPLETE][8] ([i915#3371])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11756/shard-iclb7/igt@gem_exec_capture@p...@vcs0.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105102v1/shard-iclb1/igt@gem_exec_capture@p...@vcs0.html
>
> * igt@gem_exec_endless@dispatch@bcs0:
> - shard-tglb: [PASS][9] -> [INCOMPLETE][10] ([i915#3778])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11756/shard-tglb2/igt@gem_exec_endless@dispa...@bcs0.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105102v1/shard-tglb1/igt@gem_exec_endless@dispa...@bcs0.html
>
> * igt@gem_exec_fair@basic-none-solo@rcs0:
> - shard-kbl: NOTRUN -> [FAIL][11] ([i915#2842])
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Extract, polish, and document multicast handling
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
&
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: Extract, polish, and document multicast handling
Yes, I see we don't have an issue. So I have created https://gitlab.freedesktop.org/drm/intel/-/issues/6246 igt@i915_module_load@load - dmesg-warn - drm_WARN_ON(lpt_iclkip_freq() != clock), WARNING: .* at drivers/gpu/drm/i915/display/intel_pch_refclk.c:\d+ lpt_program_iclkip Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Wednesday, June 15, 2022 2:05 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana ; Syrjala, Ville Subject: Re: ✗ Fi.CI.BAT: failure for i915: Extract, polish, and document multicast handling On Wed, Jun 15, 2022 at 01:03:06AM +, 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 -> Patchwork_105134v1 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_105134v1 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_105134v1, please notify your bug team 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_105134v1/index.html > > Participating hosts (43 -> 43) > -- > > Additional (2): fi-hsw-4770 bat-dg2-9 > Missing(2): bat-atsm-1 fi-bdw-samus > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_105134v1: > > ### IGT changes ### > > Possible regressions > > * igt@i915_module_load@load: > - fi-hsw-4770:NOTRUN -> [DMESG-WARN][1] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-hsw-477 > 0/igt@i915_module_l...@load.html <4> [25.955765] i915 :00:02.0: drm_WARN_ON(lpt_iclkip_freq() != clock) <4> [25.955785] WARNING: CPU: 3 PID: 99 at drivers/gpu/drm/i915/display/intel_pch_refclk.c:182 lpt_program_iclkip+0x268/0x2f0 [i915] This display warning is unrelated to GT multicast, so not caused by this series. I don't see any similar gitlab issues that match this, but the warning itself only landed in i915 yesterday in this series: https://patchwork.freedesktop.org/series/103491/ so it's possible this is a known preexisting problem that just has a new warning signature now and needs a new filter. +Cc Ville as the author of that series. Matt > > > Known issues > > > Here are the changes found in Patchwork_105134v1 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@i915_selftest@live@gem: > - fi-blb-e6850: NOTRUN -> [DMESG-FAIL][2] ([i915#4528]) >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-blb-e6850/igt@i915_selftest@l...@gem.html > - fi-pnv-d510:NOTRUN -> [DMESG-FAIL][3] ([i915#4528]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-pnv-d51 > 0/igt@i915_selftest@l...@gem.html > > * igt@i915_selftest@live@hangcheck: > - bat-dg1-6: [PASS][4] -> [DMESG-FAIL][5] ([i915#4494] / > [i915#4957]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11758/bat-dg1-6/igt@i915_selftest@l...@hangcheck.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/bat-dg1-6/ > igt@i915_selftest@l...@hangcheck.html > > * igt@i915_suspend@basic-s2idle-without-i915: > - bat-dg1-5: NOTRUN -> [INCOMPLETE][6] ([i915#6011]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/bat-dg1-5/ > igt@i915_susp...@basic-s2idle-without-i915.html > > * igt@kms_chamelium@common-hpd-after-suspend: > - fi-bsw-n3050: NOTRUN -> [SKIP][7] ([fdo#109271] / [fdo#111827]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-bsw-n30 > 50/igt@kms_chamel...@common-hpd-after-suspend.html > > * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: > - fi-bsw-n3050: NOTRUN -> [SKIP][8] ([fdo#109271]) >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-bsw-n30 > 50/igt@kms_pipe_crc_ba...@suspend-read-crc-pipe-a.html > > * igt@runner@aborted: > - fi-hsw-4770:NOTRUN -> [FAIL][9] ([i915#4312] / [i915#5594]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105134v1/fi-hsw-477 > 0/igt@run...@aborted.html > > > Possible fixes > > * igt@
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Adjust EU per SS according to HAS_ONE_EU_PER_FUSE_BIT()
Comments below -Original Message- From: Roper, Matthew D Sent: Tuesday, June 14, 2022 2:17 PM To: Vudum, Lakshminarayana Cc: intel-gfx@lists.freedesktop.org Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/pvc: Adjust EU per SS according to HAS_ONE_EU_PER_FUSE_BIT() Looks like the logs links finally work (there was probably a big backlog to upload them after the gitlab downtime). The module_reload log shows and ext4 filesystem panic (not graphics-related). The syncobj_basic failure is an unexpected incomplete; no graphics errors in the log that I can see, although logs of periodic non-graphics warnings from xhci_hcd. Matt On Tue, Jun 14, 2022 at 01:21:49PM -0700, Vudum, Lakshminarayana wrote: > I am unable to load both the failures? Is there any other way to get these > failures? > > -Original Message- > From: Roper, Matthew D > Sent: Tuesday, June 14, 2022 1:07 PM > To: intel-gfx@lists.freedesktop.org > Cc: Vudum, Lakshminarayana > Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/pvc: Adjust EU per SS > according to HAS_ONE_EU_PER_FUSE_BIT() > > On Tue, Jun 14, 2022 at 07:20:48PM +, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915/pvc: Adjust EU per SS according to > > HAS_ONE_EU_PER_FUSE_BIT() > > URL : https://patchwork.freedesktop.org/series/105010/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_11753_full -> Patchwork_105010v1_full > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_105010v1_full absolutely > > need to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_105010v1_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 -> 13) > > -- > > > > No changes in participating hosts > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > > Patchwork_105010v1_full: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@i915_module_load@reload-with-fault-injection: > > - shard-snb: [PASS][1] -> [DMESG-WARN][2] > >[1]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-snb5/igt@i915_module_l...@reload-with-fault-injection.html > >[2]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105010v1/shard-snb5/igt@i915_module_l...@reload-with-fault-injection.html > > Lakshmi: This failure is same as https://gitlab.freedesktop.org/drm/intel/-/issues/6201 > > * igt@syncobj_basic@bad-create-flags: > > - shard-skl: NOTRUN -> [INCOMPLETE][3] > >[3]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105010v1/shard-skl3/igt@syncobj_ba...@bad-create-flags.html > Lakshmi: We have a bug for similar signature https://gitlab.freedesktop.org/drm/intel/-/issues/2295 ' This test didn't produce any output. The machine probably rebooted ungracefully.' > The failure logs for the two hits above don't seem to have been uploaded > to the server so I can't see exactly what went wrong. However this > patch is modifying xehp_sseu_info_init() which only gets executed on > Xe_HP-based platforms, so it would not change the behavior of SNB or > SKL. > > > Matt > > > > > > > Known issues > > > > > > Here are the changes found in Patchwork_105010v1_full that come from > > known issues: > > > > ### CI changes ### > > > > Issues hit > > > > * boot: > > - shard-apl: ([PASS][4], [PASS][5], [PASS][6], [PASS][7], > > [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], > > [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], > > [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], > > [PASS][26], [PASS][27], [PASS][28]) -> ([PASS][29], [PASS][30], [FAIL][31], > > [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], > > [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], > > [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], > > [PASS][50], [PASS][51], [PASS][52], [PASS][53]) ([i915#4386]) > >[4]: > > https://intel-gfx-ci.
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pvc: Adjust EU per SS according to HAS_ONE_EU_PER_FUSE_BIT()
I am unable to load both the failures? Is there any other way to get these failures? -Original Message- From: Roper, Matthew D Sent: Tuesday, June 14, 2022 1:07 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/pvc: Adjust EU per SS according to HAS_ONE_EU_PER_FUSE_BIT() On Tue, Jun 14, 2022 at 07:20:48PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/pvc: Adjust EU per SS according to HAS_ONE_EU_PER_FUSE_BIT() > URL : https://patchwork.freedesktop.org/series/105010/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11753_full -> Patchwork_105010v1_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_105010v1_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_105010v1_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 -> 13) > -- > > No changes in participating hosts > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_105010v1_full: > > ### IGT changes ### > > Possible regressions > > * igt@i915_module_load@reload-with-fault-injection: > - shard-snb: [PASS][1] -> [DMESG-WARN][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-snb5/igt@i915_module_l...@reload-with-fault-injection.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105010v1/shard-snb5/igt@i915_module_l...@reload-with-fault-injection.html > > * igt@syncobj_basic@bad-create-flags: > - shard-skl: NOTRUN -> [INCOMPLETE][3] >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105010v1/shard-skl3/igt@syncobj_ba...@bad-create-flags.html The failure logs for the two hits above don't seem to have been uploaded to the server so I can't see exactly what went wrong. However this patch is modifying xehp_sseu_info_init() which only gets executed on Xe_HP-based platforms, so it would not change the behavior of SNB or SKL. Matt > > > Known issues > > > Here are the changes found in Patchwork_105010v1_full that come from known > issues: > > ### CI changes ### > > Issues hit > > * boot: > - shard-apl: ([PASS][4], [PASS][5], [PASS][6], [PASS][7], > [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], > [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], > [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], > [PASS][26], [PASS][27], [PASS][28]) -> ([PASS][29], [PASS][30], [FAIL][31], > [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], > [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], > [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], > [PASS][50], [PASS][51], [PASS][52], [PASS][53]) ([i915#4386]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl1/boot.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl1/boot.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl1/boot.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl1/boot.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl2/boot.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl2/boot.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl2/boot.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl2/boot.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl3/boot.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl3/boot.html >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl3/boot.html >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl4/boot.html >[16]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl4/boot.html >[17]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl4/boot.html >[18]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl6/boot.html >[19]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11753/shard-apl6/boot.html >[
Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: More PVC+DG2 workarounds
No Idea about that Matt. I have never did that. Lakshmi. -Original Message- From: Roper, Matthew D Sent: Tuesday, June 7, 2022 9:43 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.SPARSE: warning for drm/i915: More PVC+DG2 workarounds On Wed, Jun 08, 2022 at 02:38:12AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915: More PVC+DG2 workarounds > URL : https://patchwork.freedesktop.org/series/104866/ > State : warning > > == Summary == > > Error: dim sparse failed > Sparse version: v0.6.2 > Fast mode used, each commit won't be checked separately. > @Lakshmi, is there any way to get more details out of these Sparse results that pop up sometimes? When I run "dim sparse" locally (both with and without --fast) I get success: Sparse version: 0.6.4 Commit: drm/i915: More PVC+DG2 workarounds Okay! and if I do it manually with "make C=1" I just see the handful of pre-existing / expected warnings, nothing new from this patch. Any ideas what could be going on here? Maybe some quirk of the older v0.6.2 version CI is running? Matt > -- Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display/adlp: More updates to voltage swing table
Failure is associated to the GEN9 generic bug and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/6075
[GEN9 only] Few tests - No logs
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Thursday, June 2, 2022 10:16 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vivekanandan, Balasubramani ; Vudum,
Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display/adlp: More
updates to voltage swing table
On Thu, Jun 02, 2022 at 04:31:23PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/display/adlp: More updates to voltage swing table
> URL : https://patchwork.freedesktop.org/series/104661/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11719 -> Patchwork_104661v1
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_104661v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_104661v1, please notify your bug team 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_104661v1/index.html
>
> Participating hosts (47 -> 43)
> --
>
> Additional (2): bat-atsm-1 fi-tgl-u2
> Missing(6): fi-hsw-4200u bat-adlm-1 fi-icl-u2 fi-bwr-2160 bat-jsl-2
> fi-bdw-samus
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_104661v1:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_softpin@allocator-basic-reserve:
> - fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11719/fi-kbl-soraka/igt@gem_soft...@allocator-basic-reserve.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-kbl-sor
> aka/igt@gem_soft...@allocator-basic-reserve.html
From the log it appears this test did complete successfully. I'm not sure why
CI marked it as an INCOMPLETE? Either way, Bala's patch here would not have
changed the behavior for a KBL platform.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_flip@basic-flip-vs-wf_vblank:
> - {bat-atsm-1}: NOTRUN -> [SKIP][3] +4 similar issues
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/bat-atsm-1
> /igt@kms_flip@basic-flip-vs-wf_vblank.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_104661v1 that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_huc_copy@huc-copy:
> - fi-tgl-u2: NOTRUN -> [SKIP][4] ([i915#2190])
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-tgl-u2/
> igt@gem_huc_c...@huc-copy.html
>
> * igt@i915_selftest@live@gt_engines:
> - bat-dg1-6: [PASS][5] -> [INCOMPLETE][6] ([i915#4418])
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11719/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/bat-dg1-6/
> igt@i915_selftest@live@gt_engines.html
>
> * igt@i915_selftest@live@hangcheck:
> - fi-bdw-5557u: NOTRUN -> [INCOMPLETE][7] ([i915#3921])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-bdw-555
> 7u/igt@i915_selftest@l...@hangcheck.html
>
> * igt@kms_chamelium@common-hpd-after-suspend:
> - fi-hsw-4770:NOTRUN -> [SKIP][8] ([fdo#109271] / [fdo#111827])
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-hsw-4770/igt@kms_chamel...@common-hpd-after-suspend.html
> - fi-cfl-8109u: NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-cfl-810
> 9u/igt@kms_chamel...@common-hpd-after-suspend.html
>
> * igt@kms_chamelium@hdmi-edid-read:
> - fi-tgl-u2: NOTRUN -> [SKIP][10] ([fdo#109284] / [fdo#111827])
> +7 similar issues
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104661v1/fi-tgl-u2/
> igt@kms_chamel...@hdmi-edid-read.html
>
> * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
> - fi-tgl-u2: NOTRUN -> [SKIP][11] ([i915#4103]) +1 similar issue
>[11]:
> https://intel-gfx-ci.01
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/hwconfig: Report no hwconfig support on ADL-N
Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6085
igt@kms_cursor_crc@pipe-a-cursor-256x256-sliding - incomplete - No
warnings/errors
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Tuesday, May 24, 2022 4:56 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vivekanandan, Balasubramani ; Vudum,
Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/hwconfig: Report no
hwconfig support on ADL-N
On Mon, May 23, 2022 at 08:16:36PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/hwconfig: Report no hwconfig support on ADL-N
> URL : https://patchwork.freedesktop.org/series/104270/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11690_full -> Patchwork_104270v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_104270v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_104270v1_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-rkl
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_104270v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@kms_cursor_crc@pipe-a-cursor-256x256-sliding:
> - shard-tglb: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11690/shard-tglb1/igt@kms_cursor_...@pipe-a-cursor-256x256-sliding.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104270v1/shard-tglb
> 8/igt@kms_cursor_...@pipe-a-cursor-256x256-sliding.html
Seems like the machine or network died; the logs just cut off with no
indication of a problem before that point. And ADL-N hwconfig change wouldn't
impact the behavior of a TGL display test, so not related to Bala's patch here.
Patch applied to drm-intel-gt-next. Thanks for the patch.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * {igt@kms_hdr@bpc-switch@pipe-a-hdmi-a-1}:
> - {shard-dg1}:NOTRUN -> [SKIP][3]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104270v1/shard-dg1-
> 16/igt@kms_hdr@bpc-swi...@pipe-a-hdmi-a-1.html
>
>
> New tests
> -
>
> New tests have been introduced between CI_DRM_11690_full and
> Patchwork_104270v1_full:
>
> ### New IGT tests (7) ###
>
> * igt@gem_busy@parallel:
> - Statuses :
> - Exec time: [None] s
>
> * igt@kms_flip@modeset-vs-vblank-race@a-dp1:
> - Statuses : 2 pass(s)
> - Exec time: [4.03, 4.20] s
>
> * igt@kms_flip@modeset-vs-vblank-race@b-dp1:
> - Statuses : 2 pass(s)
> - Exec time: [3.92, 4.06] s
>
> * igt@kms_flip@modeset-vs-vblank-race@c-dp1:
> - Statuses : 2 pass(s)
> - Exec time: [3.99, 4.11] s
>
> * igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
> - Statuses : 1 pass(s)
> - Exec time: [11.53] s
>
> * igt@perf_pmu@busy-accuracy-2:
> - Statuses :
> - Exec time: [None] s
>
> * igt@perf_pmu@most-busy-idle-check-all:
> - Statuses :
> - Exec time: [None] s
>
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_104270v1_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@feature_discovery@display-2x:
> - shard-iclb: NOTRUN -> [SKIP][4] ([i915#1839])
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104270v1/shard-iclb
> 5/igt@feature_discov...@display-2x.html
>
> * igt@gem_exec_fair@basic-deadline:
> - shard-kbl: NOTRUN -> [FAIL][5] ([i915#2846])
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104270v1/shard-kbl6/igt@gem_exec_f...@basic-deadline.html
> - shard-apl: NOTRUN -> [FAIL][6] ([i915#2846])
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104270v1/shard-apl2
> /igt@gem_exec_f...@basic-deadline.html
>
> * igt@gem_exec_fair@basic-none@vecs0:
> - shard-apl: [PASS][7] -> [FAIL][8] ([i915#2842]) +1 similar
> issue
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11690/shard-apl6/igt@gem_e
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/hwconfig: Future-proof platform checks
Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6086
igt@kms_atomic_transition@modeset-transition-nonblocking-fencing@1x-outputs -
incomplete - No warnings/errors
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Wednesday, May 25, 2022 8:23 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/hwconfig: Future-proof platform
checks
On Wed, May 25, 2022 at 06:41:11AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/hwconfig: Future-proof platform checks
> URL : https://patchwork.freedesktop.org/series/104338/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11696_full -> Patchwork_104338v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_104338v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_104338v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_104338v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> *
> igt@kms_atomic_transition@modeset-transition-nonblocking-fencing@1x-outputs:
> - shard-tglb: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11696/shard-tglb3/igt@kms_atomic_transition@modeset-transition-nonblocking-fenc...@1x-outputs.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-tglb
> 8/igt@kms_atomic_transition@modeset-transition-nonblocking-fencing@1x-
> outputs.html
Unexpected incomplete; not errors in the log before the machine/network
disappeared. Not related to this series.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_color@pipe-a-deep-color:
> - {shard-rkl}:[SKIP][3] ([i915#4070] / [i915#4098]) ->
> [INCOMPLETE][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11696/shard-rkl-2/igt@kms_co...@pipe-a-deep-color.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-rkl-
> 6/igt@kms_co...@pipe-a-deep-color.html
>
> *
> {igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-25@pipe-a-edp-1}:
> - shard-tglb: [SKIP][5] ([i915#5176]) -> [SKIP][6] +19 similar
> issues
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11696/shard-tglb7/igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0...@pipe-a-edp-1.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-tglb
> 5/igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-25@pip
> e-a-edp-1.html
>
> *
> {igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-5@pipe-a-edp-1}:
> - shard-iclb: NOTRUN -> [SKIP][7] +2 similar issues
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-iclb
> 6/igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-5@pipe
> -a-edp-1.html
>
> *
> {igt@kms_plane_scaling@plane-downscale-with-rotation-factor-0-75@pipe-a-edp-1}:
> - shard-iclb: [SKIP][8] ([i915#5176]) -> [SKIP][9] +17 similar
> issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11696/shard-iclb8/igt@kms_plane_scaling@plane-downscale-with-rotation-factor-0...@pipe-a-edp-1.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-iclb
> 3/igt@kms_plane_scaling@plane-downscale-with-rotation-factor-0-75@pipe
> -a-edp-1.html
>
> * {igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-a-edp-1}:
> - {shard-rkl}:NOTRUN -> [SKIP][10] +4 similar issues
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104338v1/shard-rkl-
> 6/igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-a-edp-1
> .html
>
> * {igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-d-hdmi-a-1}:
> - {shard-tglu}: [SKIP][11] ([i915#5176]) -> [SKIP][12] +15 similar
> issues
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11696/shard-tglu-5/igt@kms_plane_scaling@plane-upscale-with-rotati
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: SSEU handling updates (rev2)
CI: boot test failure seems to fail always in the same manner. https://gitlab.freedesktop.org/drm/intel/-/issues/6074 BDW: CI:Boot - fail - No warnings/errors I believe the shards failures is unrelated (as there no logs) to this patch. So I created a generic bug for GEN9 to track of failures that doesn't have logs. This bug will be reviewed weekly by the team. https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/shard-skl3/igt@i915_selftest@l...@dmabuf.html https://gitlab.freedesktop.org/drm/intel/-/issues/6075 Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Monday, May 23, 2022 4:32 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for i915: SSEU handling updates (rev2) On Mon, May 23, 2022 at 09:23:33PM +, Patchwork wrote: > == Series Details == > > Series: i915: SSEU handling updates (rev2) > URL : https://patchwork.freedesktop.org/series/104244/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11693 -> Patchwork_104244v2 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_104244v2 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_104244v2, please notify your bug team 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_104244v2/index.html > > Participating hosts (44 -> 45) > -- > > Additional (2): fi-icl-u2 fi-tgl-u2 > Missing(1): fi-hsw-4770 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_104244v2: > > ### CI changes ### > > Possible regressions > > * boot: > - fi-bdw-5557u: [PASS][1] -> [FAIL][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/fi-bdw-5557u/boot.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-bdw-555 > 7u/boot.html I don't see a boot failure here? It looks like i915 loaded successfully, without errors. It also looks like more tests ran successfully on the machine after that as well. Matt > > > Known issues > > > Here are the changes found in Patchwork_104244v2 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_exec_gttfill@basic: > - fi-icl-u2: NOTRUN -> [INCOMPLETE][3] ([i915#4890]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-icl-u2/ > igt@gem_exec_gttf...@basic.html > > * igt@gem_huc_copy@huc-copy: > - fi-tgl-u2: NOTRUN -> [SKIP][4] ([i915#2190]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/ > igt@gem_huc_c...@huc-copy.html > > * igt@i915_selftest@live@hangcheck: > - bat-dg1-6: [PASS][5] -> [DMESG-FAIL][6] ([i915#4494] / > [i915#4957]) >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/bat-dg1-6/igt@i915_selftest@l...@hangcheck.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/bat-dg1-6/igt@i915_selftest@l...@hangcheck.html > - fi-snb-2600:[PASS][7] -> [INCOMPLETE][8] ([i915#3921]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-snb-260 > 0/igt@i915_selftest@l...@hangcheck.html > > * igt@kms_busy@basic@flip: > - fi-tgl-u2: NOTRUN -> [DMESG-WARN][9] ([i915#402]) +3 similar > issues >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/ > igt@kms_busy@ba...@flip.html > > * igt@kms_chamelium@dp-hpd-fast: > - fi-tgl-u2: NOTRUN -> [SKIP][10] ([fdo#109284] / [fdo#111827]) > +7 similar issues >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/ > igt@kms_chamel...@dp-hpd-fast.html > > * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: > - fi-tgl-u2: NOTRUN -> [SKIP][11] ([i915#4103]) +1 similar issue >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/ > igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html > > * igt@kms_flip@basic-flip-vs-modeset@b-edp1: > - bat-adlp-4: [PASS][12] -> [DMESG-WARN][13] ([i915#3576]) >[12]: >
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5
I don't see any regressions from Bat but on shards. https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-skl8/igt@i915_pm...@dc5-dpms.html is mapped to https://gitlab.freedesktop.org/drm/intel/-/issues/5961 Thanks, Lakshmi. -Original Message- From: Srivatsa, Anusha Sent: Saturday, May 21, 2022 9:13 AM To: Roper, Matthew D ; intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5 > -Original Message- > From: Roper, Matthew D > Sent: Friday, May 20, 2022 4:11 PM > To: intel-gfx@lists.freedesktop.org > Cc: Srivatsa, Anusha ; Vudum, > Lakshminarayana > Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable > DC5 > > On Fri, May 20, 2022 at 05:11:22PM +, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915/dg2: Enable DC5 > > URL : https://patchwork.freedesktop.org/series/104233/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_11681 -> Patchwork_104233v1 > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_104233v1 absolutely > need to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_104233v1, please notify your bug team 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_104233v1/index.ht > > ml > > > > Participating hosts (46 -> 44) > > -- > > > > Missing(2): bat-dg2-8 fi-rkl-11600 > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > Patchwork_104233v1: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@fbdev@read: > > - fi-icl-u2: [PASS][1] -> [DMESG-WARN][2] > >[1]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/fi-icl- > u2/igt@fb...@read.html > >[2]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/fi-icl-u > > 2/ > > igt@fb...@read.html > > It looks like this is an error coming from a bluetooth driver, not > related to > graphics: > ><3> [26.916574] Bluetooth: hci0: Reading Intel version command > failed (- > 110) ><4> [26.916689] general protection fault, probably for > non-canonical address 0x6b6b6b6b6b6b6b6b: [#1] PREEMPT SMP NOPTI ><4> [26.916726] CPU: 2 PID: 99 Comm: kworker/2:2 Not tainted > 5.18.0-rc7- Patchwork_104233v1-gba369855d857+ #1 ><4> [26.916731] Hardware name: Intel Corporation Ice Lake Client > Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS > ICLSFWR1.R00.3183.A00.1905020411 05/02/2019 ><4> [26.916737] Workqueue: events hci_cmd_timeout [bluetooth] ><4> [26.916755] RIP: 0010:hci_cmd_timeout+0x30/0xa0 [bluetooth] ><4> [26.916806] Code: ff ff 53 48 8b 87 10 05 00 00 48 89 fb 48 85 > c0 74 63 > 48 8b 80 b8 00 00 00 48 8d b5 a0 00 00 00 48 85 ed 48 c7 c7 c8 6c 38 > a0 <0f> > b7 10 48 c7 c0 53 38 38 a0 48 0f 44 f0 e8 91 13 06 00 48 8b 83 ><4> [26.916814] RSP: 0018:c9ae3e50 EFLAGS: 00010286 ><4> [26.916818] RAX: 6b6b6b6b6b6b6b6b RBX: 88810ef5aac8 RCX: > ><4> [26.916821] RDX: 0001 RSI: 88810ef5a0a0 RDI: > a0386cc8 ><4> [26.916825] RBP: 88810ef5a000 R08: 88810700ba38 R09: > fffe ><4> [26.916828] R10: 0001 R11: dfbbfb17 R12: > 88849fb3afc0 ><4> [26.916832] R13: 88849fb3fc00 R14: R15: > 88849fb3fc05 ><4> [26.916835] FS: () > GS:88849fb0() > knlGS: ><4> [26.916839] CS: 0010 DS: ES: CR0: 80050033 ><4> [26.916842] CR2: 7fcc6837e1a0 CR3: 06612006 CR4: > 00770ee0 ><4> [26.916846] PKRU: 5554 ><4> [26.916848] Call Trace: ><4> [26.916850] ><4> [26.916852] process_one_work+0x272/0x5c0 ><4> [26.916857] worker_thread+0x37/0x370 ><4> [26.916861] ? process_one_work+0x5c0/0x5c0 ><4> [26.916864] kthread+0xed/0x120 ><4> [26.916867] ? kthread_comp
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5
Issue is part of https://gitlab.freedesktop.org/drm/intel/-/issues/4890.
Filter is updated to include all tests.
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Friday, May 20, 2022 4:11 PM
To: intel-gfx@lists.freedesktop.org
Cc: Srivatsa, Anusha ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5
On Fri, May 20, 2022 at 05:11:22PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dg2: Enable DC5
> URL : https://patchwork.freedesktop.org/series/104233/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11681 -> Patchwork_104233v1
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_104233v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_104233v1, please notify your bug team 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_104233v1/index.html
>
> Participating hosts (46 -> 44)
> --
>
> Missing(2): bat-dg2-8 fi-rkl-11600
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_104233v1:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@fbdev@read:
> - fi-icl-u2: [PASS][1] -> [DMESG-WARN][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/fi-icl-u2/igt@fb...@read.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/fi-icl-u2/
> igt@fb...@read.html
It looks like this is an error coming from a bluetooth driver, not related to
graphics:
<3> [26.916574] Bluetooth: hci0: Reading Intel version command failed (-110)
<4> [26.916689] general protection fault, probably for non-canonical address
0x6b6b6b6b6b6b6b6b: [#1] PREEMPT SMP NOPTI
<4> [26.916726] CPU: 2 PID: 99 Comm: kworker/2:2 Not tainted
5.18.0-rc7-Patchwork_104233v1-gba369855d857+ #1
<4> [26.916731] Hardware name: Intel Corporation Ice Lake Client
Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS
ICLSFWR1.R00.3183.A00.1905020411 05/02/2019
<4> [26.916737] Workqueue: events hci_cmd_timeout [bluetooth]
<4> [26.916755] RIP: 0010:hci_cmd_timeout+0x30/0xa0 [bluetooth]
<4> [26.916806] Code: ff ff 53 48 8b 87 10 05 00 00 48 89 fb 48 85 c0 74 63
48 8b 80 b8 00 00 00 48 8d b5 a0 00 00 00 48 85 ed 48 c7 c7 c8 6c 38 a0 <0f> b7
10 48 c7 c0 53 38 38 a0 48 0f 44 f0 e8 91 13 06 00 48 8b 83
<4> [26.916814] RSP: 0018:c9ae3e50 EFLAGS: 00010286
<4> [26.916818] RAX: 6b6b6b6b6b6b6b6b RBX: 88810ef5aac8 RCX:
<4> [26.916821] RDX: 0001 RSI: 88810ef5a0a0 RDI:
a0386cc8
<4> [26.916825] RBP: 88810ef5a000 R08: 88810700ba38 R09:
fffe
<4> [26.916828] R10: 0001 R11: dfbbfb17 R12:
88849fb3afc0
<4> [26.916832] R13: 88849fb3fc00 R14: R15:
88849fb3fc05
<4> [26.916835] FS: () GS:88849fb0()
knlGS:
<4> [26.916839] CS: 0010 DS: ES: CR0: 80050033
<4> [26.916842] CR2: 7fcc6837e1a0 CR3: 06612006 CR4:
00770ee0
<4> [26.916846] PKRU: 5554
<4> [26.916848] Call Trace:
<4> [26.916850]
<4> [26.916852] process_one_work+0x272/0x5c0
<4> [26.916857] worker_thread+0x37/0x370
<4> [26.916861] ? process_one_work+0x5c0/0x5c0
<4> [26.916864] kthread+0xed/0x120
<4> [26.916867] ? kthread_complete_and_exit+0x20/0x20
<4> [26.916870] ret_from_fork+0x1f/0x30
<4> [26.916875]
Looks like this might be
https://gitlab.freedesktop.org/drm/intel/-/issues/4890 ?
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_busy@basic@modeset:
> - {bat-dg2-9}:[PASS][3] -> [DMESG-WARN][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/bat-dg2-9/igt@kms_busy@ba...@modeset.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/bat-dg2-9/
> igt@kms_busy@ba...@modeset.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_104233v1 that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: SSEU handling updates (rev4)
Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6038 igt@kms_flip@flip-vs-panning-interruptible@c-edp1 - dmesg-warn - rcu: INFO: rcu_preempt detected stalls on CPUs/tasks Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Tuesday, May 17, 2022 8:24 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for i915: SSEU handling updates (rev4) On Wed, May 18, 2022 at 12:34:11AM +, Patchwork wrote: > == Series Details == > > Series: i915: SSEU handling updates (rev4) > URL : https://patchwork.freedesktop.org/series/103244/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11666_full -> Patchwork_103244v4_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_103244v4_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_103244v4_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (11 -> 11) > -- > > No changes in participating hosts > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_103244v4_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_flip@flip-vs-panning-interruptible@c-edp1: > - shard-iclb: [PASS][1] -> [DMESG-WARN][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11666/shard-iclb3/igt@kms_flip@flip-vs-panning-interrupti...@c-edp1.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/shard-iclb8/igt@kms_flip@flip-vs-panning-interrupti...@c-edp1.html <3> [607.307030] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: <3> [607.307121] rcu: 3-...!: (159 GPs behind) idle=834/0/0x0 softirq=27765/27765 fqs=1 (false positive?) <3> [607.307825] rcu: 7-...!: (172 GPs behind) idle=abc/0/0x0 softirq=23642/23643 fqs=1 (false positive?) <4> [607.307934](detected by 0, t=65002 jiffies, g=64137, q=5840) <6> [607.307942] Sending NMI from CPU 0 to CPUs 3: <4> [607.308032] NMI backtrace for cpu 3 skipped: idling at intel_idle+0x67/0xc0 <6> [607.308950] Sending NMI from CPU 0 to CPUs 7: <4> [607.309045] NMI backtrace for cpu 7 skipped: idling at intel_idle+0x67/0xc0 <3> [607.309957] rcu: rcu_preempt kthread timer wakeup didn't happen for 64995 jiffies! g64137 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 <3> [607.310053] rcu: Possible timer handling issue on cpu=3 timer-softirq=16787 <3> [607.310110] rcu: rcu_preempt kthread starved for 64998 jiffies! g64137 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=3 <3> [607.310195] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. <3> [607.310267] rcu: RCU grace-period kthread stack dump: <6> [607.310310] task:rcu_preempt state:I stack:14472 pid: 13 ppid: 2 flags:0x4000 <6> [607.310326] Call Trace: <6> [607.310330] <6> [607.310339] __schedule+0x483/0xb50 <6> [607.310353] ? schedule_timeout+0x1b9/0x2e0 <6> [607.310367] schedule+0x3f/0xa0 <6> [607.310376] schedule_timeout+0x1be/0x2e0 <6> [607.310386] ? del_timer_sync+0xb0/0xb0 <6> [607.310398] ? 0x8100 <6> [607.310408] ? rcu_gp_cleanup+0x440/0x440 <6> [607.310413] rcu_gp_fqs_loop+0x273/0x3b0 <6> [607.310427] rcu_gp_kthread+0xb8/0x120 <6> [607.310436] kthread+0xed/0x120 <6> [607.310443] ? kthread_complete_and_exit+0x20/0x20 <6> [607.310452] ret_from_fork+0x1f/0x30 <6> [607.310478] <3> [607.310481] rcu: Stack dump where RCU GP kthread last ran: <6> [607.310527] Sending NMI from CPU 0 to CPUs 3: <4> [607.310602] NMI backtrace for cpu 3 skipped: idling at intel_idle+0x67/0xc0 It's not clear what this is from (no indication it's even related to the graphics driver). Definitely not the kind of thing that the SSEU rework in this series could cause to happen during a display test. Matt > > > Known issues > > > Here are the changes found in Patchwork_103244v4_full that come from known > issues: > > ### CI changes ### > > Possible fixes > > * boot: > - shard-skl: ([PASS][3], [PASS][4], [PASS][5], [PASS][6], > [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], > [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], > [PASS][
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: SSEU handling updates (rev4)
Since it's bat failure, I have filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/6025 igt@prime_vgem@basic-fence-read - incomplete - No warnings/errors Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Tuesday, May 17, 2022 12:20 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for i915: SSEU handling updates (rev4) On Tue, May 17, 2022 at 07:08:08PM +, Patchwork wrote: > == Series Details == > > Series: i915: SSEU handling updates (rev4) > URL : https://patchwork.freedesktop.org/series/103244/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11666 -> Patchwork_103244v4 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_103244v4 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_103244v4, please notify your bug team 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_103244v4/index.html > > Participating hosts (41 -> 41) > -- > > Additional (1): fi-skl-guc > Missing(1): bat-rpls-2 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_103244v4: > > ### IGT changes ### > > Possible regressions > > * igt@prime_vgem@basic-fence-read: > - fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11666/fi-kbl-soraka/igt@prime_v...@basic-fence-read.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-kbl-sor > aka/igt@prime_v...@basic-fence-read.html The results link shows 'SUCCESS' so I'm not sure why this was marked as INCOMPLETE here? Doesn't appear to be related to this series. Matt > > > Known issues > > > Here are the changes found in Patchwork_103244v4 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_lmem_swapping@basic: > - fi-skl-guc: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#4613]) +3 > similar issues >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-skl-guc > /igt@gem_lmem_swapp...@basic.html > > * igt@i915_selftest@live@execlists: > - fi-bsw-kefka: [PASS][4] -> [INCOMPLETE][5] ([i915#2940] / > [i915#5801]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11666/fi-bsw-kefka/igt@i915_selftest@l...@execlists.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-bsw-kef > ka/igt@i915_selftest@l...@execlists.html > > * igt@i915_selftest@live@gem: > - fi-pnv-d510:NOTRUN -> [DMESG-FAIL][6] ([i915#4528]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-pnv-d51 > 0/igt@i915_selftest@l...@gem.html > > * igt@i915_selftest@live@hangcheck: > - fi-snb-2600:[PASS][7] -> [INCOMPLETE][8] ([i915#3921]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11666/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-snb-260 > 0/igt@i915_selftest@l...@hangcheck.html > > * igt@kms_chamelium@dp-crc-fast: > - fi-skl-guc: NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827]) > +8 similar issues >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-skl-guc > /igt@kms_chamel...@dp-crc-fast.html > > * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: > - fi-skl-guc: NOTRUN -> [SKIP][10] ([fdo#109271]) +11 similar > issues >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-skl-guc > /igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html > > * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d: > - fi-skl-guc: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#533]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-skl-guc > /igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-d.html > > * igt@runner@aborted: > - fi-bsw-kefka: NOTRUN -> [FAIL][12] ([fdo#109271] / [i915#3428] / > [i915#4312]) >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103244v4/fi-bsw-kef > ka/igt@run...@aborted.html > > > Possible fixes > >
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Media freq factor and per-gt enhancements/fixes (rev6)
I have reopened the https://gitlab.freedesktop.org/drm/intel/-/issues/4440
igt@prime_self_import@reimport-vs-gem_close-race - fail - Failed assertion:
obj_count == 0,error: -2 != 0
"{igt@i915_pm_freq_mult@media-freq@gt0" is not yet in CI bug log.
Thanks,
Lakshmi.
-Original Message-
From: Dixit, Ashutosh
Sent: Friday, May 13, 2022 12:19 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Media freq factor and per-gt
enhancements/fixes (rev6)
On Thu, 12 May 2022 23:58:55 -0700, Patchwork wrote:
>
> Patch Details
>
> Series: drm/i915: Media freq factor and per-gt enhancements/fixes (rev6)
> URL: https://patchwork.freedesktop.org/series/102665/
> State: failure
> Details:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102665v6/index.html
>
> CI Bug Log - changes from CI_DRM_11646_full -> Patchwork_102665v6_full
>
> FAILURE
>
> Possible regressions
>
> * {igt@i915_pm_freq_mult@media-freq@gt0} (NEW):
>
> * shard-iclb: NOTRUN -> SKIP
This skip is expected, this new IGT will skip on unsupported platforms.
>
> * igt@prime_self_import@export-vs-gem_close-race:
>
> * shard-tglb: PASS -> FAIL
This failure is unrelated. It is seen here too:
https://patchwork.freedesktop.org/series/99867/
Thanks.
--
Ashutosh
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Introduce Ponte Vecchio (rev4)
Correct, I have added GLK to this bug https://gitlab.freedesktop.org/drm/intel/-/issues/5753 Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Wednesday, May 11, 2022 1:45 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for i915: Introduce Ponte Vecchio (rev4) On Wed, May 11, 2022 at 07:45:28PM +, Patchwork wrote: > == Series Details == > > Series: i915: Introduce Ponte Vecchio (rev4) > URL : https://patchwork.freedesktop.org/series/103443/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11632_full -> Patchwork_103443v4_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_103443v4_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_103443v4_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (12 -> 11) > -- > > Missing(1): shard-rkl > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_103443v4_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_busy@close-race: > - shard-glk: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-glk4/igt@gem_b...@close-race.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v4/shard-glk8 > /igt@gem_b...@close-race.html Doesn't seem to be related to the PVC changes here. Maybe https://gitlab.freedesktop.org/drm/intel/-/issues/5753 but on a different platform? Matt > > > Known issues > > > Here are the changes found in Patchwork_103443v4_full that come from known > issues: > > ### CI changes ### > > Possible fixes > > * boot: > - shard-apl: ([PASS][3], [PASS][4], [PASS][5], [PASS][6], > [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], > [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], > [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], > [PASS][25], [FAIL][26], [PASS][27]) ([i915#4386]) -> ([PASS][28], [PASS][29], > [PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], > [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], > [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], > [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl8/boot.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl8/boot.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl8/boot.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl7/boot.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl7/boot.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl7/boot.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl6/boot.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl6/boot.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl6/boot.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl6/boot.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl4/boot.html >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl4/boot.html >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl4/boot.html >[16]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl3/boot.html >[17]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl3/boot.html >[18]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl3/boot.html >[19]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl3/boot.html >[20]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl3/boot.html >[21]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl2/boot.html >[22]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl2/boot.html >[23]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11632/shard-apl2/boot.html >[24]: > https://inte
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Introduce Ponte Vecchio
igt@kms_concurrent@pipe-b@hdmi-a-3 is not yet in CBL, otherwise failures are
addressed and are-reported.
-Original Message-
From: Roper, Matthew D
Sent: Tuesday, May 3, 2022 10:33 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for i915: Introduce Ponte Vecchio
On Mon, May 02, 2022 at 10:58:32PM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915: Introduce Ponte Vecchio
> URL : https://patchwork.freedesktop.org/series/103443/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11588_full -> Patchwork_103443v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_103443v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_103443v1_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 -> 13)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_103443v1_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_pm_rpm@system-suspend-modeset:
> - shard-kbl: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11588/shard-kbl4/igt@i915_pm_...@system-suspend-modeset.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-kbl6
> /igt@i915_pm_...@system-suspend-modeset.html
https://gitlab.freedesktop.org/drm/intel/-/issues/3614
>
> * {igt@kms_concurrent@pipe-b@hdmi-a-3} (NEW):
> - {shard-dg1}:NOTRUN -> [CRASH][3] +1 similar issue
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-dg1-
> 18/igt@kms_concurrent@pip...@hdmi-a-3.html
https://gitlab.freedesktop.org/drm/intel/-/issues/4886
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw:
> - shard-tglb: [PASS][4] -> [INCOMPLETE][5]
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11588/shard-tglb7/igt@kms_frontbuffer_track...@fbcpsr-1p-pri-indfb-multidraw.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-tglb
> 8/igt@kms_frontbuffer_track...@fbcpsr-1p-pri-indfb-multidraw.html
No obvious warnings/errors. Maybe the same as
https://gitlab.freedesktop.org/drm/intel/-/issues/5756 ?
None of the changes here are caused by the PVC series. I'm going to apply
patch #1 to drm-intel-gt-next to get the ball rolling on having the basic
IS_PONTEVECCHIO() definition in the tree (which will help cut down on future
cross-tree dependencies).
We'll hold off on applying any of the others until after the next
drm-intel-gt-next pull requests gets sent.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_pm_rpm@gem-evict-pwrite:
> - {shard-rkl}:[PASS][6] -> [INCOMPLETE][7] +1 similar issue
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11588/shard-rkl-5/igt@i915_pm_...@gem-evict-pwrite.html
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-rkl-
> 5/igt@i915_pm_...@gem-evict-pwrite.html
>
> * igt@i915_pm_rpm@system-suspend-devices:
> - {shard-dg1}:NOTRUN -> [INCOMPLETE][8] +3 similar issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-dg1-
> 18/igt@i915_pm_...@system-suspend-devices.html
>
> * igt@i915_selftest@live:
> - {shard-rkl}:NOTRUN -> [INCOMPLETE][9]
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103443v1/shard-rkl-
> 5/igt@i915_selft...@live.html
>
>
> New tests
> -
>
> New tests have been introduced between CI_DRM_11588_full and
> Patchwork_103443v1_full:
>
> ### New IGT tests (2) ###
>
> * igt@kms_concurrent@pipe-a@hdmi-a-3:
> - Statuses : 1 crash(s)
> - Exec time: [0.03] s
>
> * igt@kms_concurrent@pipe-b@hdmi-a-3:
> - Statuses : 1 crash(s)
> - Exec time: [0.04] s
>
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_103443v1_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@api_intel_bb@blit-reloc-keep-cache:
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Media freq factor and per-gt enhancements/fixes (rev4)
Re-reported and few comments below.
-Original Message-
From: Dixit, Ashutosh
Sent: Friday, April 29, 2022 5:45 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Media freq factor and per-gt
enhancements/fixes (rev4)
On Fri, 29 Apr 2022 16:38:35 -0700, Patchwork wrote:
>
> Possible regressions
>
> * igt@gem_eio@in-flight-suspend:
>
> * shard-skl: PASS -> INCOMPLETE
This failure in unrelated.
>
> * {igt@i915_pm_disag_freq@media-freq@gt0} (NEW):
>
> * shard-iclb: NOTRUN -> SKIP
>
> * shard-tglb: NOTRUN -> SKIP
These failures are expected, the test will skip on platforms which do not
support this feature.
Lakshmi: These tests are not in yet in CI bug log.
>
> * igt@kms_draw_crc@draw-method-xrgb2101010-mmap-gtt-xtiled:
>
> * shard-kbl: PASS -> FAIL
This failure in unrelated.
Lakshmi: Filed https://gitlab.freedesktop.org/drm/intel/-/issues/5870
igt@kms_draw_crc@draw-method-xrgb2101010-mmap-gtt-xtiled - fail - Failed
assertion: rc == 0
> New tests
>
> New tests have been introduced between CI_DRM_11583_full and
> Patchwork_102665v4_full:
>
> New IGT tests (1)
>
> * igt@i915_pm_disag_freq@media-freq@gt0:
>
> * Statuses : 7 skip(s)
> * Exec time: [0.0] s
These skips are the same as above and expected.
Thanks.
--
Ashutosh
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Fix memory leaks in per-gt sysfs
Addressed the failure and re-reported. Re-opened the issue https://gitlab.freedesktop.org/drm/intel/-/issues/5196 igt@syncobj_timeline@wait-all-for-submit-snapshot - fail - Failed assertion: __syncobj_timeline_wait_ioctl(wait->fd, >wait) == 0, error: -62 != 0 Filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/5864 igt@kms_flip@flip-vs-suspend-interruptible@a-edp1 - incomplete - PM: suspend entry (deep) Thanks, Lakshmi. -Original Message- From: Dixit, Ashutosh Sent: Wednesday, April 27, 2022 5:42 PM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/gt: Fix memory leaks in per-gt sysfs On Wed, 27 Apr 2022 15:45:40 -0700, Patchwork wrote: > > Possible regressions > > * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1: > > * shard-skl: PASS -> INCOMPLETE > > * igt@syncobj_timeline@wait-all-for-submit-snapshot: > > * shard-skl: PASS -> FAIL > > Warnings > > * igt@gem_eio@unwedge-stress: > > * shard-tglb: FAIL (i915#232) -> FAIL +1 similar issue These failures are unrelated, the patch is related only to per-gt sysfs.
Re: [Intel-gfx] False-positive of CI issue w/ AMDGPU patch set
Both are known failures, so I have re-reported. Thanks, Lakshmi. From: Zhang, Dingchen (David) Sent: Tuesday, April 26, 2022 10:48 AM To: Vudum, Lakshminarayana ; intel-gfx@lists.freedesktop.org; Latvala, Petri Cc: Siqueira, Rodrigo ; Pillai, Aurabindo Subject: Re: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] Hi Lakshmi, Thanks for the clarification and now the rev5 CI build reports issue again which is false-positive (as below) https://patchwork.freedesktop.org/series/102886/ [cid:image003.png@01D859BA.7EDAB080] [cid:image004.png@01D859BA.7EDAB080] Could you help clear it? Thanks David From: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Sent: Tuesday, April 26, 2022 11:25 AM To: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org> mailto:intel-gfx@lists.freedesktop.org>>; Latvala, Petri mailto:petri.latv...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pillai, Aurabindo mailto:aurabindo.pil...@amd.com>> Subject: RE: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] I have re-opened https://gitlab.freedesktop.org/drm/intel/-/issues/5302<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Fintel%2F-%2Fissues%2F5302=05%7C01%7CDingchen.Zhang%40amd.com%7C8305d0dcfdc14eb5043408da27991099%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865835617158995%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=yxB2PcUIWOfFOotlCMvSyzUYy4lYG7iurxSc1%2FiXSVo%3D=0> igt@i915_module_load@reload-with-fault-injection - dmesg-warn - WARNING: .* at drivers/gpu/drm/i915/i915_vma.c:\d+ i915_ggtt_pin Other sounds is not totally new, I have seen similar signature few months ago on a different test but to me this sounds like a sporadic issue. So filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/5844<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Fintel%2F-%2Fissues%2F5844=05%7C01%7CDingchen.Zhang%40amd.com%7C8305d0dcfdc14eb5043408da27991099%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865835617158995%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=gliMh56K68thW3KnSp9prTIEPIsNNQiSZvXRNNNRGos%3D=0> igt@kms_fbcon_fbt@psr-suspend - incomplete - pstore logs - is trying to acquire lock at: down_trylock, but task is already holding lock at: raw_spin_rq_lock_nested Anyways, re-reporting doesn't really help as we will get results from rev5. Lakshmi. From: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>> Sent: Tuesday, April 26, 2022 6:38 AM To: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>; Latvala, Petri mailto:petri.latv...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pillai, Aurabindo mailto:aurabindo.pil...@amd.com>> Subject: Re: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] Hi Lakshmi, Thanks for your reply and could you please clear another false-positive CI issue below? (link https://patchwork.freedesktop.org/series/102886/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fseries%2F102886%2F=05%7C01%7CDingchen.Zhang%40amd.com%7C8305d0dcfdc14eb5043408da27991099%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865835617158995%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=3bT4vEBbsQL3vFhWTyryZph7TQ3VwAe1%2Fdce%2FQG02uE%3D=0>). The possible regression is not correlated to the amdgpu patch set. [cid:image005.png@01D859BA.7EDAB080] regards David From: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Sent: Monday, April 25, 2022 5:25 PM To: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org> mailto:intel-gfx@lists.freedesktop.org>>; Latvala, Petri mailto:petri.latv...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pillai, Aurabindo mailto:aurabindo.pil...@amd.com>> Subject: RE: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] I am not sure if I can take any action here. @Latvala, Petri<mailto:petri.latv...@intel.com> Any inputs? Lakshmi. From: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>> Sent: Monday, April 25, 2022 1:16 PM To: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pilla
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: Upstream initial DG2 PCI IDs
Yes, I have filed a new issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/5846
igt@kms_vblank@pipe-d-wait-idle-hang - incomplete - general protection fault,
probably for non-canonical address 0x380015ffd0003c, RIP:
0010:acpi_ns_search_one_scope
Thanks,
Lakshmi
-Original Message-
From: Roper, Matthew D
Sent: Tuesday, April 26, 2022 10:06 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for i915: Upstream initial DG2 PCI IDs
On Tue, Apr 26, 2022 at 12:17:24AM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915: Upstream initial DG2 PCI IDs
> URL : https://patchwork.freedesktop.org/series/103098/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11550_full -> Patchwork_103098v1_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_103098v1_full absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_103098v1_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (10 -> 13)
> --
>
> Additional (3): shard-rkl shard-dg1 shard-tglu
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_103098v1_full:
>
> ### CI changes ###
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * boot:
> - {shard-rkl}:NOTRUN -> ([PASS][1], [PASS][2], [PASS][3],
> [PASS][4], [PASS][5], [PASS][6], [PASS][7], [FAIL][8], [PASS][9], [PASS][10],
> [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16],
> [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21])
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-6/boot.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-2/boot.html
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-2/boot.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-3/boot.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-3/boot.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-4/boot.html
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-5/boot.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-
> 5/boot.html
THere doesn't seem to be a log output for the failure. But updating DG2 device
IDs shouldn't have any impact on RKL.
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-5/boot.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-6/boot.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-6/boot.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[15]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[16]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[17]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-1/boot.html
>[18]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-2/boot.html
>[19]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-2/boot.html
>[20]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-2/boot.html
>[21]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-rkl-
> 2/boot.html
>
>
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@kms_vblank@pipe-d-wait-idle-hang:
> - shard-tglb: [PASS][22] -> [INCOMPLETE][23]
>[22]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11550/shard-tglb6/igt@kms_vbl...@pipe-d-wait-idle-hang.html
>[23]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/shard-tglb
> 3/igt@kms_vbl...@pipe-d-wait-idle-hang.html
GPF outside of i915:
<4> [358.240067] general protect
Re: [Intel-gfx] False-positive of CI issue w/ AMDGPU patch set
I have re-opened https://gitlab.freedesktop.org/drm/intel/-/issues/5302 igt@i915_module_load@reload-with-fault-injection - dmesg-warn - WARNING: .* at drivers/gpu/drm/i915/i915_vma.c:\d+ i915_ggtt_pin Other sounds is not totally new, I have seen similar signature few months ago on a different test but to me this sounds like a sporadic issue. So filed a new issue https://gitlab.freedesktop.org/drm/intel/-/issues/5844 igt@kms_fbcon_fbt@psr-suspend - incomplete - pstore logs - is trying to acquire lock at: down_trylock, but task is already holding lock at: raw_spin_rq_lock_nested Anyways, re-reporting doesn't really help as we will get results from rev5. Lakshmi. From: Zhang, Dingchen (David) Sent: Tuesday, April 26, 2022 6:38 AM To: Vudum, Lakshminarayana ; intel-gfx@lists.freedesktop.org; Latvala, Petri Cc: Siqueira, Rodrigo ; Pillai, Aurabindo Subject: Re: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] Hi Lakshmi, Thanks for your reply and could you please clear another false-positive CI issue below? (link https://patchwork.freedesktop.org/series/102886/). The possible regression is not correlated to the amdgpu patch set. [cid:image001.png@01D85947.3E2D5CE0] regards David From: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Sent: Monday, April 25, 2022 5:25 PM To: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>>; intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org> mailto:intel-gfx@lists.freedesktop.org>>; Latvala, Petri mailto:petri.latv...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pillai, Aurabindo mailto:aurabindo.pil...@amd.com>> Subject: RE: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] I am not sure if I can take any action here. @Latvala, Petri<mailto:petri.latv...@intel.com> Any inputs? Lakshmi. From: Zhang, Dingchen (David) mailto:dingchen.zh...@amd.com>> Sent: Monday, April 25, 2022 1:16 PM To: Vudum, Lakshminarayana mailto:lakshminarayana.vu...@intel.com>> Cc: Siqueira, Rodrigo mailto:rodrigo.sique...@amd.com>>; Pillai, Aurabindo mailto:aurabindo.pil...@amd.com>> Subject: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] Hi Lakshminarayana, Could you help clear the CI pipeline issue of below patch w/ the ARMHF failure, which is a false-positive that is uncorrelated to the amdgpu patch set? https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/569071<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fgfx-ci%2Figt-ci-tags%2F-%2Fpipelines%2F569071=05%7C01%7CDingchen.Zhang%40amd.com%7C6d2f17cdd4a94409438908da27021633%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865187176641298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2FosUCKthERnkC1UKo1f30wFjzDXPnx49CigQ49r13Ks%3D=0> [Image removed by sender.]<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fgfx-ci%2Figt-ci-tags%2F-%2Fpipelines%2F569071=05%7C01%7CDingchen.Zhang%40amd.com%7C6d2f17cdd4a94409438908da27021633%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865187176641298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2FosUCKthERnkC1UKo1f30wFjzDXPnx49CigQ49r13Ks%3D=0> Pipeline * gfx-ci / igt-ci-tags<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fgfx-ci%2Figt-ci-tags%2F-%2Fpipelines%2F569071=05%7C01%7CDingchen.Zhang%40amd.com%7C6d2f17cdd4a94409438908da27021633%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865187176641298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2FosUCKthERnkC1UKo1f30wFjzDXPnx49CigQ49r13Ks%3D=0> CI tags for IGT GPU tools. WARNING: This repo's master branch will not be updated. Use https://gitlab.freedesktop.org/drm/igt-gpu-tools for this purpose. gitlab.freedesktop.org https://patchwork.freedesktop.org/series/102886/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fseries%2F102886%2F=05%7C01%7CDingchen.Zhang%40amd.com%7C6d2f17cdd4a94409438908da27021633%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865187176641298%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2BDpEt1mqHO94oUE%2Fj4H2fGN85nWLcOzLcM8DtHpYdyw%3D=0> Thanks David
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: Upstream initial DG2 PCI IDs
Filed https://gitlab.freedesktop.org/drm/intel/-/issues/5827 igt@gem_exec_suspend@basic-s0@smem - incomplete - pstore logs - BUG: kernel NULL pointer dereference, address: 0008, RIP: 0010:aq_ring_rx_fill Lakshmi. -Original Message- From: Roper, Matthew D Sent: Monday, April 25, 2022 3:20 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for i915: Upstream initial DG2 PCI IDs On Mon, Apr 25, 2022 at 09:58:43PM +, Patchwork wrote: > == Series Details == > > Series: i915: Upstream initial DG2 PCI IDs > URL : https://patchwork.freedesktop.org/series/103098/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11550 -> Patchwork_103098v1 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_103098v1 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_103098v1, please notify your bug team 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_103098v1/index.html > > Participating hosts (43 -> 44) > -- > > Additional (2): bat-dg2-8 bat-dg1-6 > Missing(1): fi-bsw-cyan > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_103098v1: > > ### IGT changes ### > > Possible regressions > > * igt@gem_exec_suspend@basic-s0@smem: > - bat-dg1-6: NOTRUN -> [INCOMPLETE][1] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103098v1/bat-dg1-6/ > igt@gem_exec_suspend@basic...@smem.html Panic from the ethernet driver (drivers/net/ethernet/aquantia/atlantic/). Not related to i915 or this series: <1>[ 232.010956] BUG: kernel NULL pointer dereference, address: 0008 <1>[ 232.010958] #PF: supervisor read access in kernel mode <1>[ 232.010959] #PF: error_code(0x) - not-present page <6>[ 232.010960] PGD 0 P4D 0 <4>[ 232.010961] Oops: [#1] PREEMPT SMP NOPTI <4>[ 232.010963] CPU: 2 PID: 5261 Comm: kworker/u12:27 Not tainted 5.18.0-rc4-Patchwork_103098v1-g56b089ae03ef+ #1 <4>[ 232.010964] Hardware name: Gigabyte Technology Co., Ltd. GB-Z390 Garuda/GB-Z390 Garuda-CF, BIOS IG1c 11/19/2019 <4>[ 232.010965] Workqueue: events_unbound async_run_entry_fn <4>[ 232.010968] RIP: 0010:aq_ring_rx_fill+0xca/0x1f0 [atlantic] <4>[ 232.010975] Code: 45 24 ba 00 00 00 00 83 c0 01 39 45 28 48 0f 46 c2 89 45 24 41 83 ee 01 0f 84 ee 00 00 00 48 8d 1c 40 48 c1 e3 04 48 03 5d 00 <48> 8b 43 08 48 c7 43 28 00 08 00 00 48 85 c0 75 85 48 8b 45 10 31 <4>[ 232.010976] RSP: 0018:c900016bbcb8 EFLAGS: 00010246 <4>[ 232.010977] RAX: RBX: RCX: <4>[ 232.010978] RDX: RSI: 0047 RDI: 888108e213a0 <4>[ 232.010979] RBP: 888108e213a0 R08: R09: 2000 <4>[ 232.010980] R10: R11: ea0004bbc7c0 R12: 1000 <4>[ 232.010980] R13: R14: R15: 8881000d8205 <4>[ 232.010981] FS: () GS:8884ad70() knlGS: <4>[ 232.010982] CS: 0010 DS: ES: CR0: 80050033 <4>[ 232.010983] CR2: 0008 CR3: 06612004 CR4: 003706e0 <4>[ 232.010983] DR0: DR1: DR2: <4>[ 232.010984] DR3: DR6: fffe0ff0 DR7: 0400 <4>[ 232.010985] Call Trace: <4>[ 232.010985] <4>[ 232.010986] aq_vec_init+0x7c/0xe0 [atlantic] <4>[ 232.010991] aq_nic_init+0xf4/0x1d0 [atlantic] <4>[ 232.010995] atl_resume_common+0x49/0xf0 [atlantic] <4>[ 232.010999] ? pci_pm_thaw+0x80/0x80 <4>[ 232.011002] dpm_run_callback+0x5c/0x240 <4>[ 232.011004] device_resume+0xb2/0x1e0 <4>[ 232.011006] ? __suspend_report_result.cold.21+0x18/0x18 <4>[ 232.011008] async_resume+0x14/0x30 <4>[ 232.011010] async_run_entry_fn+0x2b/0x130 <4>[ 232.011012] process_one_work+0x275/0x5c0 <4>[ 232.011014] worker_thread+0x37/0x370 <4>[ 232.011015] ? process_one_work+0x5c0/0x5c0 <4>[ 232.011016] kthread+0xef/0x120 <4>[ 232.011017] ? kthread_complete_and_exit+0x20/0x20 <4>[ 232.011019] ret_from_fork+0x22/0x30 <4>[ 232.011022] <4>[ 232.011022] Modu
Re: [Intel-gfx] False-positive of CI issue w/ AMDGPU patch set
I am not sure if I can take any action here. @Latvala, Petri<mailto:petri.latv...@intel.com> Any inputs? Lakshmi. From: Zhang, Dingchen (David) Sent: Monday, April 25, 2022 1:16 PM To: Vudum, Lakshminarayana Cc: Siqueira, Rodrigo ; Pillai, Aurabindo Subject: False-positive of CI issue w/ AMDGPU patch set [AMD Official Use Only] Hi Lakshminarayana, Could you help clear the CI pipeline issue of below patch w/ the ARMHF failure, which is a false-positive that is uncorrelated to the amdgpu patch set? https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/569071 [Image removed by sender.]<https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/569071> Pipeline * gfx-ci / igt-ci-tags<https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/569071> CI tags for IGT GPU tools. WARNING: This repo's master branch will not be updated. Use https://gitlab.freedesktop.org/drm/igt-gpu-tools for this purpose. gitlab.freedesktop.org https://patchwork.freedesktop.org/series/102886/ Thanks David
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses
I see bat results went through successfully. But on shards, there is a boot failure from ICL, where I am unable to load the result page(html). Lakshmi. -Original Message- From: Deak, Imre Sent: Friday, April 22, 2022 2:39 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses Hi Lakshmi, On Thu, Apr 21, 2022 at 09:08:29PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses > URL : https://patchwork.freedesktop.org/series/102941/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11537 -> Patchwork_102941v1 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_102941v1 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_102941v1, please notify your bug team 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_102941v1/index.html > > Participating hosts (45 -> 45) > -- > > Additional (2): fi-bdw-gvtdvm fi-bdw-5557u > Missing(2): fi-bsw-cyan fi-icl-u2 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_102941v1: > > ### IGT changes ### > > Possible regressions > > * igt@i915_selftest@live@gem: > - fi-tgl-1115g4: [PASS][1] -> [DMESG-WARN][2] +15 similar issues >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11537/fi-tgl-1115g4/igt@i915_selftest@l...@gem.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/fi-tgl-111 > 5g4/igt@i915_selftest@l...@gem.html This is "i915 :00:02.0: [drm] *ERROR* power well AUX_TBT4 state mismatch (refcount 1/enabled 0)" tracked at https://gitlab.freedesktop.org/drm/intel/-/issues/2867 The issue is unrelated to the change, since fi-tgl-111g4 doesn't have an eDP panel. For 2867 I will follow up with a patch to change the error to a debug message, since TBT power wells are expected to stay disabled on a disconnected port. > Known issues > > > Here are the changes found in Patchwork_102941v1 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@fbdev@write: > - fi-bdw-gvtdvm: NOTRUN -> [SKIP][3] ([fdo#109271]) +5 similar issues >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/fi-bdw-gvt > dvm/igt@fb...@write.html > > * igt@gem_exec_suspend@basic-s0@smem: > - fi-bdw-gvtdvm: NOTRUN -> [INCOMPLETE][4] ([i915#4831]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/fi-bdw-gvt > dvm/igt@gem_exec_suspend@basic...@smem.html > > * igt@i915_selftest@live@execlists: > - fi-bsw-n3050: [PASS][5] -> [INCOMPLETE][6] ([i915#2940]) >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11537/fi-bsw-n3050/igt@i915_selftest@l...@execlists.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/fi-bsw-n30 > 50/igt@i915_selftest@l...@execlists.html > > * igt@i915_selftest@live@gt_engines: > - bat-dg1-6: [PASS][7] -> [INCOMPLETE][8] ([i915#4418]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11537/bat-dg1-6/igt@i915_selftest@live@gt_engines.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/bat-dg1-6/ > igt@i915_selftest@live@gt_engines.html > > * igt@i915_selftest@live@hangcheck: > - fi-hsw-g3258: [PASS][9] -> [INCOMPLETE][10] ([i915#4785]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11537/fi-hsw-g3258/igt@i915_selftest@l...@hangcheck.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/fi-hsw-g32 > 58/igt@i915_selftest@l...@hangcheck.html > > * igt@i915_selftest@live@slpc: > - bat-dg1-5: [PASS][11] -> [INCOMPLETE][12] ([i915#5198]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11537/bat-dg1-5/igt@i915_selftest@l...@slpc.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102941v1/bat-dg1-5/ > igt@i915_selftest@l...@slpc.html > > * igt@kms_flip@basic-flip-vs-modeset@b-edp1: > - bat-adlp-4: [PASS][13] -> [DMESG-WARN][14] ([i915#3576]) +1 > similar issue >[13]: > https://intel-gfx-ci.01.org/t
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,v2,01/18] drm/i915: Move per-platform power well hooks to intel_display_power_well.c (rev2)
Imre, I have addressed the failure and re-reported. -Original Message- From: Deak, Imre Sent: Tuesday, April 19, 2022 1:28 PM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [CI,v2,01/18] drm/i915: Move per-platform power well hooks to intel_display_power_well.c (rev2) Hi Lakshmi, On Fri, Apr 15, 2022 at 10:24:03AM +, Patchwork wrote: > == Series Details == > > Series: series starting with [CI,v2,01/18] drm/i915: Move per-platform power > well hooks to intel_display_power_well.c (rev2) > URL : https://patchwork.freedesktop.org/series/102719/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11504_full -> Patchwork_102719v2_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_102719v2_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_102719v2_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (12 -> 11) > -- > > Missing(1): shard-rkl > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_102719v2_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c: > - shard-skl: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11504/shard-skl2/igt@kms_pipe_crc_ba...@suspend-read-crc-pipe-c.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-skl6 > /igt@kms_pipe_crc_ba...@suspend-read-crc-pipe-c.html The issue looks unrelated, the changes should not affect the behavior and checking the order/dependencies of enabled/disabled power wells in the above logs confirms this. It's probably the general issue affecting all S3 suspend tests on all the SKL shard machines (all of those are the same/similar model afaik) vs. the BAT SKL machines without any trace of this problem (fi-skl-6700k2, fi-skl-guc). One previous instance of the same issue is at: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11487/shard-skl7/igt@kms_pipe_crc_ba...@suspend-read-crc-pipe-b.html One theory is that the machines don't support S3 at all or well (they only support S0ix) or that some other peripheral causes the problem. I'll try to borrow one of these systems and check out this. > Known issues > > > Here are the changes found in Patchwork_102719v2_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_eio@kms: > - shard-tglb: [PASS][3] -> [FAIL][4] ([i915#232]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11504/shard-tglb7/igt@gem_...@kms.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-tglb > 5/igt@gem_...@kms.html > > * igt@gem_eio@unwedge-stress: > - shard-skl: [PASS][5] -> [TIMEOUT][6] ([i915#3063]) >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11504/shard-skl7/igt@gem_...@unwedge-stress.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-skl4 > /igt@gem_...@unwedge-stress.html > > * igt@gem_exec_fair@basic-pace-share@rcs0: > - shard-tglb: [PASS][7] -> [FAIL][8] ([i915#2842]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11504/shard-tglb6/igt@gem_exec_fair@basic-pace-sh...@rcs0.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-tglb > 6/igt@gem_exec_fair@basic-pace-sh...@rcs0.html > > * igt@gem_exec_flush@basic-wb-prw-default: > - shard-snb: [PASS][9] -> [SKIP][10] ([fdo#109271]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11504/shard-snb4/igt@gem_exec_fl...@basic-wb-prw-default.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-snb6 > /igt@gem_exec_fl...@basic-wb-prw-default.html > > * igt@gem_lmem_swapping@heavy-random: > - shard-skl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102719v2/shard-skl3 > /igt@gem_lmem_swapp...@heavy-random.html > > * igt@gem_lmem_swapping@heavy-verify-random: > - shard-apl: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613]) >[12]: > https://intel-gfx-ci.
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v3,1/2] drm/dp: Factor out a function to probe a DPCD address (rev3)
Re-reported. -Original Message- From: Deak, Imre Sent: Thursday, April 14, 2022 11:33 AM To: intel-gfx@lists.freedesktop.org; Nikula, Jani ; Almahallawy, Khaled Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [v3,1/2] drm/dp: Factor out a function to probe a DPCD address (rev3) On Mon, Apr 11, 2022 at 08:18:39PM +, Patchwork wrote: > == Series Details == > > Series: series starting with [v3,1/2] drm/dp: Factor out a function to probe > a DPCD address (rev3) > URL : https://patchwork.freedesktop.org/series/102428/ > State : failure I pushed patch 1/2 to drm-misc-next, thanks for the reviews. The failure is unrelated, see below. > == Summary == > > CI Bug Log - changes from CI_DRM_11482_full -> Patchwork_102428v3_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_102428v3_full absolutely need > to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_102428v3_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 -> 10) > -- > > Missing(3): shard-rkl shard-dg1 shard-tglu > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_102428v3_full: > > ### IGT changes ### > > Possible regressions > > * igt@i915_pm_rpm@system-suspend-modeset: > - shard-skl: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11482/shard-skl10/igt@i915_pm_...@system-suspend-modeset.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-skl6 > /igt@i915_pm_...@system-suspend-modeset.html There's only eDP on this machine, where the changes should make no difference. In previous CI_DRM results I can see quite a few incompletes during suspend tests on the shard-skl machines, while can't see any such on other skls (fi-skl-6700k2, fi-skl-guc). > Known issues > > > Here are the changes found in Patchwork_102428v3_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_ctx_sseu@invalid-args: > - shard-apl: NOTRUN -> [SKIP][3] ([fdo#109271]) +119 similar > issues >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-apl1 > /igt@gem_ctx_s...@invalid-args.html > > * igt@gem_exec_balancer@parallel-contexts: > - shard-kbl: NOTRUN -> [DMESG-WARN][4] ([i915#5076] / > [i915#5614]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-kbl3 > /igt@gem_exec_balan...@parallel-contexts.html > > * igt@gem_exec_fair@basic-deadline: > - shard-glk: [PASS][5] -> [FAIL][6] ([i915#2846]) >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11482/shard-glk1/igt@gem_exec_f...@basic-deadline.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-glk2 > /igt@gem_exec_f...@basic-deadline.html > > * igt@gem_exec_fair@basic-none@vcs0: > - shard-glk: [PASS][7] -> [FAIL][8] ([i915#2842]) >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11482/shard-glk4/igt@gem_exec_fair@basic-n...@vcs0.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-glk1 > /igt@gem_exec_fair@basic-n...@vcs0.html > > * igt@gem_exec_fair@basic-pace-solo@rcs0: > - shard-kbl: [PASS][9] -> [FAIL][10] ([i915#2842]) +1 similar > issue >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11482/shard-kbl4/igt@gem_exec_fair@basic-pace-s...@rcs0.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-kbl7 > /igt@gem_exec_fair@basic-pace-s...@rcs0.html > > * igt@gem_exec_flush@basic-batch-kernel-default-uc: > - shard-snb: [PASS][11] -> [SKIP][12] ([fdo#109271]) +4 similar > issues >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11482/shard-snb2/igt@gem_exec_fl...@basic-batch-kernel-default-uc.html >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-snb6 > /igt@gem_exec_fl...@basic-batch-kernel-default-uc.html > > * igt@gem_exec_params@rsvd2-dirt: > - shard-iclb: NOTRUN -> [SKIP][13] ([fdo#109283]) >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102428v3/shard-iclb > 6/igt@gem_exec_par...@rsvd2-dirt.html >
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Media freq factor and per-gt enhancements/fixes
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/5701 Re-reported. Lakshmi. -Original Message- From: Dixit, Ashutosh Sent: Wednesday, April 13, 2022 10:57 PM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Media freq factor and per-gt enhancements/fixes On Wed, 13 Apr 2022 18:00:29 -0700, Patchwork wrote: > > > Possible regressions > > * igt@gem_lmem_swapping@parallel-random-engines: > > * bat-dg1-5: NOTRUN -> FAIL > > * bat-dg1-6: NOTRUN -> FAIL These failures are unrelated. They are showing up everywhere and causing all recent pre-merge CI results to show false positives. Please take a look. Thanks.
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: Add DRM_I915_QUERY_GEOMETRY_SUBSLICES uapi
Yeah that something new https://gitlab.freedesktop.org/drm/intel/-/issues/5631 igt@i915_selftest@live@gt_engines - fail - rcs0 Mismatch between ring timestamp and walltime! i915/live_engine_pm_selftests: live_engine_timestamps failed with error -22 Thanks, Lakshmi. -Original Message- From: Roper, Matthew D Sent: Monday, April 11, 2022 8:11 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for i915: Add DRM_I915_QUERY_GEOMETRY_SUBSLICES uapi On Tue, Apr 12, 2022 at 12:43:28AM +, Patchwork wrote: > == Series Details == > > Series: i915: Add DRM_I915_QUERY_GEOMETRY_SUBSLICES uapi > URL : https://patchwork.freedesktop.org/series/102553/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11484 -> Patchwork_102553v1 > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_102553v1 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_102553v1, please notify your bug team 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_102553v1/index.html > > Participating hosts (49 -> 36) > -- > > Additional (1): fi-hsw-4770 > Missing(14): shard-tglu bat-dg1-6 bat-dg2-8 shard-rkl bat-dg2-9 > fi-bsw-cyan bat-adlp-6 bat-adlp-4 fi-kbl-x1275 bat-rpls-1 bat-rpls-2 > shard-dg1 bat-jsl-2 bat-jsl-1 > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_102553v1: > > ### IGT changes ### > > Possible regressions > > * igt@i915_selftest@live@gt_engines: > - fi-glk-j4005: [PASS][1] -> [FAIL][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11484/fi-glk-j4005/igt@i915_selftest@live@gt_engines.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-glk-j40 > 05/igt@i915_selftest@live@gt_engines.html (i915_selftest:5830) igt_kmod-WARNING: rcs0 elapsed:100430ns, CTX_TIMESTAMP:145261ns, RING_TIMESTAMP:145261ns (i915_selftest:5830) igt_kmod-WARNING: rcs0 Mismatch between ring timestamp and walltime! (i915_selftest:5830) igt_kmod-WARNING: i915/live_engine_pm_selftests: live_engine_timestamps failed with error -22 Doesn't appear to be related to this series since the query interface isn't being used by the test. I don't see any similar failures from a quick fdo search though. Matt > > > Known issues > > > Here are the changes found in Patchwork_102553v1 that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_softpin@allocator-basic-reserve: > - fi-hsw-4770:NOTRUN -> [SKIP][3] ([fdo#109271]) +9 similar issues >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-hsw-477 > 0/igt@gem_soft...@allocator-basic-reserve.html > > * igt@i915_pm_backlight@basic-brightness: > - fi-hsw-4770:NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#3012]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-hsw-477 > 0/igt@i915_pm_backli...@basic-brightness.html > > * igt@kms_chamelium@dp-crc-fast: > - fi-hsw-4770:NOTRUN -> [SKIP][5] ([fdo#109271] / [fdo#111827]) > +8 similar issues >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-hsw-477 > 0/igt@kms_chamel...@dp-crc-fast.html > > * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d: > - fi-hsw-4770:NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#533]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-hsw-477 > 0/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-d.html > > * igt@kms_psr@primary_mmap_gtt: > - fi-hsw-4770:NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#1072]) +3 > similar issues >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-hsw-477 > 0/igt@kms_psr@primary_mmap_gtt.html > > * igt@runner@aborted: > - fi-bdw-5557u: NOTRUN -> [FAIL][8] ([i915#4312]) >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102553v1/fi-bdw-555 > 7u/igt@run...@aborted.html > > > Possible fixes > > * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c: > - fi-cfl-8109u: [DMESG-WARN][9] ([i915#5341] / [i915#62]) -> > [PASS][10] >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_1148
Re: [Intel-gfx] [PATCH] drm/i915/dg2: Do not explode on phy calibration error
ICL issue is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/4767
igt@kms_fbcon_fbt@fbc(-suspend)? - fail - Failed assertion:
feature->wait_until_update(drm)
Thanks,
Lakshmi.
-Original Message-
From: De Marchi, Lucas
Sent: Monday, April 11, 2022 11:17 AM
To: Roper, Matthew D
Cc: intel-gfx@lists.freedesktop.org; Ville Syrjälä
; Jani Nikula ;
Vudum, Lakshminarayana
Subject: Re: [PATCH] drm/i915/dg2: Do not explode on phy calibration error
On Mon, Apr 11, 2022 at 08:34:35AM -0700, Matt Roper wrote:
>On Sat, Apr 09, 2022 at 11:15:36PM -0700, Lucas De Marchi wrote:
>> When the PHY fails on calibration we were previously skipping the ddi
>> initialization. However the driver is not really prepared for that,
>> ultimately leading to a NULL pointer dereference:
>>
>> [ 75.748348] i915 :03:00.0: [drm:intel_modeset_init_nogem [i915]] SNPS
>> PHY A failed to calibrate; output will not be used.
>> ...
>> [ 75.750336] i915 :03:00.0: [drm:intel_modeset_setup_hw_state [i915]]
>> [CRTC:80:pipe A] hw state readout: enabled
>> ...
>>
>> ( no DDI A/PHY A )
>> [ 75.753080] i915 :03:00.0: [drm:intel_modeset_setup_hw_state [i915]]
>> [ENCODER:235:DDI B/PHY B] hw state readout: disabled, pipe A
>> [ 75.753164] i915 :03:00.0: [drm:intel_modeset_setup_hw_state [i915]]
>> [ENCODER:245:DDI C/PHY C] hw state readout: disabled, pipe A
>> ...
>> [ 75.754425] i915 :03:00.0: [drm] *ERROR* crtc 80: Can't calculate
>> constants, dotclock = 0!
>> [ 75.765558] i915 :03:00.0:
>> drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev))
>> [ 75.765569] WARNING: CPU: 5 PID: 1759 at drivers/gpu/drm/drm_vblank.c:728
>> drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x347/0x360
>> ...
>> [ 75.781230] BUG: kernel NULL pointer dereference, address:
>> 007c
>> [ 75.788198] #PF: supervisor read access in kernel mode
>> [ 75.793347] #PF: error_code(0x) - not-present page
>> [ 75.798480] PGD 0 P4D 0
>> [ 75.801019] Oops: [#1] PREEMPT SMP NOPTI
>> [ 75.805377] CPU: 5 PID: 1759 Comm: modprobe Tainted: GW
>> 5.18.0-rc1-demarchi+ #199
>> [ 75.827613] RIP: 0010:icl_aux_power_well_disable+0x3b/0x200 [i915]
>> [ 75.833890] Code: 83 ec 30 65 48 8b 04 25 28 00 00 00 48 89 44 24 28 48
>> 8b 06 0f b6 70 1c f6 40 20 04 8d 56 fa 0f 45 f2 e8 88 bd ff ff 48 89 ef <8b>
>> 70 7c e8 ed 67 ff ff 48 89 ef 89 c6 e8 73 67 ff ff 84 c0 75 0a
>> [ 75.852629] RSP: 0018:c90003a7fb30 EFLAGS: 00010246
>> [ 75.857852] RAX: RBX: 8881145e8f10 RCX:
>>
>> [ 75.864978] RDX: 888115220840 RSI: RDI:
>> 88811522
>> [ 75.872106] RBP: 88811522 R08: 8ee8 R09:
>> fffd
>> [ 75.879234] R10: 8e20 R11: 8ed0 R12:
>> 8881145e8f10
>> [ 75.886363] R13: 0001 R14: 888115223240 R15:
>>
>> [ 75.893490] FS: 7ff6e753a740() GS:8f68()
>> knlGS:
>> [ 75.901573] CS: 0010 DS: ES: CR0: 80050033
>> [ 75.907313] CR2: 007c CR3: 0001216a6001 CR4:
>> 00770ee0
>> [ 75.914446] PKRU: 5554
>> [ 75.917153] Call Trace:
>> [ 75.919603]
>> [ 75.921709] intel_power_domains_sanitize_state+0x88/0xb0 [i915]
>> [ 75.927814] intel_modeset_init_nogem+0x317/0xef0 [i915]
>> [ 75.933205] i915_driver_probe+0x5f6/0xdf0 [i915]
>> [ 75.937976] i915_pci_probe+0x51/0x1d0 [i915]
>>
>> We skip the initialization of PHY A, but later we try to find out
>> what is the phy for that power well and dereference dig_port, which is NULL.
>>
>> Failing the PHY calibration could be left as a warning or error, like
>> it was before commit b4eb76d82a0e ("drm/i915/dg2: Skip output init on
>> PHY calibration failure"). However that often fails for outputs not
>> being used, which would make the warning/error appear on systems that
>> have no visible issues. Anyway, there is still a need to fix those
>> failures, but that is left for later.
>>
>> Signed-off-by: Lucas De Marchi
>
>Reviewed-by: Matt Roper
The only CI failure is on ICL, that doesn't have snps phy. +Lakshmi
Applied to drm-intel-next. Thanks.
Lucas De Marchi
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL (rev2)
Issues are related to following (just filed #5614) https://gitlab.freedesktop.org/drm/intel/-/issues/636 [CI][DRMTIP]igt@kms_flip@2x-flip-vs-suspend - dmesg-warn - WARNING: CPU: \d PID: \d+ at drivers/misc/mei/hbm.c:\d+ mei_hbm_dispatch\+.* https://gitlab.freedesktop.org/drm/intel/-/issues/5614 igt@gem_exec_balancer@.* - dmesg-warn/dmesg-fail - WARNING: .* at drivers/dma-buf/dma-resv.c:\d+ dma_resv_add_fence Lakshmi. -Original Message- From: Roper, Matthew D Sent: Friday, April 8, 2022 12:00 PM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL (rev2) On Fri, Apr 08, 2022 at 06:47:48PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL > (rev2) > URL : https://patchwork.freedesktop.org/series/102352/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22829_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_22829_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_22829_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (11 -> 10) > -- > > Missing(1): shard-tglu > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_22829_full: > > ### IGT changes ### > > Possible regressions > > * igt@kms_flip@flip-vs-suspend@c-dp1: > - shard-kbl: [PASS][1] -> [DMESG-WARN][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl4/igt@kms_flip@flip-vs-susp...@c-dp1.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-kbl1/ig > t@kms_flip@flip-vs-susp...@c-dp1.html Non-graphics error. Appears to be the same one reported in https://gitlab.freedesktop.org/drm/intel/-/issues/636 Not caused by this patch. Matt > > > Warnings > > * igt@gem_exec_balancer@parallel-bb-first: > - shard-iclb: [SKIP][3] ([i915#4525]) -> [DMESG-WARN][4] >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb3/igt@gem_exec_balan...@parallel-bb-first.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-iclb2/i > gt@gem_exec_balan...@parallel-bb-first.html > > * igt@gem_exec_balancer@parallel-ordering: > - shard-iclb: [SKIP][5] ([i915#4525]) -> [DMESG-FAIL][6] >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb7/igt@gem_exec_balan...@parallel-ordering.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-iclb4/i > gt@gem_exec_balan...@parallel-ordering.html > > > New tests > - > > New tests have been introduced between CI_DRM_11477_full and > Patchwork_22829_full: > > ### New Piglit tests (1) ### > > * spec@arb_copy_image@arb_copy_image-formats --samples=8: > - Statuses : 1 fail(s) > - Exec time: [2.36] s > > > > Known issues > > > Here are the changes found in Patchwork_22829_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_ctx_isolation@preservation-s3@rcs0: > - shard-apl: [PASS][7] -> [DMESG-WARN][8] ([i915#180]) +2 > similar issues >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl4/igt@gem_ctx_isolation@preservation...@rcs0.html >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-apl4/ig > t@gem_ctx_isolation@preservation...@rcs0.html > > * igt@gem_exec_capture@pi@bcs0: > - shard-skl: NOTRUN -> [INCOMPLETE][9] ([i915#4547]) >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-skl8/ig > t@gem_exec_capture@p...@bcs0.html > > * igt@gem_exec_fair@basic-none@vcs1: > - shard-kbl: NOTRUN -> [FAIL][10] ([i915#2842]) >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard-kbl7/ig > t@gem_exec_fair@basic-n...@vcs1.html > > * igt@gem_exec_fair@basic-pace@vcs1: > - shard-iclb: NOTRUN -> [FAIL][11] ([i915#2842]) +1 similar issue >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22829/shard
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display: Fix warnings about PSR lock not held (rev3)
Issue is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/5602
All tests - *ERROR* Scratch setup failed, DEBUG_LOCKS_WARN_ON(lock->magic !=
lock)
Lakshmi.
From: Souza, Jose
Sent: Thursday, April 7, 2022 2:05 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/display: Fix warnings about PSR
lock not held (rev3)
On Thu, 2022-04-07 at 21:01 +, Patchwork wrote:
Patch Details
Series:
drm/i915/display: Fix warnings about PSR lock not held (rev3)
URL:
https://patchwork.freedesktop.org/series/102298/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/index.html
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22818
Summary
FAILURE
Serious unknown changes coming with Patchwork_22818 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22818, please notify your bug team 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_22818/index.html
Participating hosts (48 -> 46)
Additional (4): bat-hsw-1 bat-rpls-2 fi-bwr-2160 bat-adlp-4
Missing (6): shard-tglu shard-rkl fi-bsw-cyan bat-rpls-1 fi-blb-e6850
fi-bdw-samus
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_22818:
CI changes
Possible regressions
* boot:
* fi-bwr-2160: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-bwr-2160/boot.html>
Hi Lakshmi
Can you please take a look at this?
There is other series with the same failure:
https://patchwork.freedesktop.org/series/102333/
IGT changes
Possible regressions
* igt@gem_lmem_swapping@basic:
* bat-dg1-5: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/bat-dg1-5/igt@gem_lmem_swapp...@basic.html>
+2 similar issues
* fi-cfl-8109u: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-cfl-8109u/igt@gem_lmem_swapp...@basic.html>
Warnings
* igt@runner@aborted:
* fi-rkl-11600:
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-rkl-11600/igt@run...@aborted.html>
(i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>) ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-rkl-11600/igt@run...@aborted.html>
* fi-kbl-guc:
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-guc/igt@run...@aborted.html>
(i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> /
i915#5257<https://gitlab.freedesktop.org/drm/intel/issues/5257>) ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-kbl-guc/igt@run...@aborted.html>
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@runner@aborted:
* {bat-hsw-1}: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/bat-hsw-1/igt@run...@aborted.html>
Known issues
Here are the changes found in Patchwork_22818 that come from known issues:
IGT changes
Issues hit
* igt@core_auth@basic-auth:
* fi-kbl-8809g: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-kbl-8809g/igt@core_a...@basic-auth.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +1 similar
issue
* igt@fbdev@eof:
* fi-kbl-8809g: NOTRUN ->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-kbl-8809g/igt@fb...@eof.html>
(i915#5557<https://gitlab.freedesktop.org/drm/intel/issues/5557>)
* igt@fbdev@write:
* bat-dg1-5: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/bat-dg1-5/igt@fb...@write.html>
(i915#2582<https://gitlab.freedesktop.org/drm/intel/issues/2582>) +4 similar
issues
* igt@gem_close_race@basic-process:
* fi-ivb-3770: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-ivb-3770/igt@gem_close_r...@basic-process.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +146 similar
issues
* igt@kms_flip@basic-flip-vs-dpms:
* fi-kbl-soraka: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-kbl-soraka/igt@kms_f...@basic-flip-vs-dpms.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +146 similar
issues
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
* fi-cfl-8109u: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22818/fi-cfl-8109u/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-b.html>
(fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +145 similar
issues
* igt@kms_pipe_crc_basic
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
Regression is related to https://gitlab.freedesktop.org/drm/intel/-/issues/5602
All tests - *ERROR* Scratch setup failed, DEBUG_LOCKS_WARN_ON(lock->magic !=
lock)
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Thursday, April 7, 2022 4:15 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Sunset igpu legacy mmap support
based on GRAPHICS_VER_FULL
On Thu, Apr 07, 2022 at 10:23:34PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
> URL : https://patchwork.freedesktop.org/series/102352/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22819
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22819 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22819, please notify your bug team 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_22819/index.html
>
> Participating hosts (49 -> 35)
> --
>
> Additional (1): fi-bwr-2160
> Missing(15): fi-bdw-samus shard-tglu bat-adls-5 bat-dg1-6 bat-dg1-5
> bat-dg2-8 shard-rkl bat-dg2-9 fi-bsw-cyan bat-adlp-6 bat-rpls-1 fi-blb-e6850
> shard-dg1 bat-jsl-2 bat-jsl-1
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22819:
>
> ### CI changes ###
>
> Possible regressions
>
> * boot:
> - fi-bwr-2160:NOTRUN -> [FAIL][1]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-bwr-2160/b
> oot.html
>
It looks like something failed during the initial driver probe (not sure what;
there don't seem to be any obvious warnings/errors) and then driver cleanup
started triggering more warnings and an eventual panic since not everything
being cleaned up had been fully setup at that point.
Not related to this patch (which shouldn't have any functional impact on any
currently-existing platform).
Matt
>
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_lmem_swapping@basic:
> - fi-cfl-8109u: NOTRUN -> [FAIL][2]
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-cfl-8109u/
> igt@gem_lmem_swapp...@basic.html
>
>
> Warnings
>
> * igt@runner@aborted:
> - fi-kbl-x1275: [FAIL][3] ([i915#4312]) -> [FAIL][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-x1275/igt@run...@aborted.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-kbl-x1275/igt@run...@aborted.html
> - fi-kbl-guc: [FAIL][5] ([i915#4312] / [i915#5257]) -> [FAIL][6]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-guc/igt@run...@aborted.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-kbl-guc/igt@run...@aborted.html
> - fi-kbl-7567u: [FAIL][7] ([i915#4312]) -> [FAIL][8]
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-7567u/igt@run...@aborted.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-kbl-7567u/
> igt@run...@aborted.html
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@runner@aborted:
> - {fi-jsl-1}: [FAIL][9] ([i915#4312]) -> [FAIL][10]
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-jsl-1/igt@run...@aborted.html
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-jsl-1/igt@
> run...@aborted.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22819 that come from known issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@core_auth@basic-auth:
> - fi-kbl-8809g: NOTRUN -> [SKIP][11] ([fdo#109271]) +1 similar issue
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-kbl-8809g/
> igt@core_a...@basic-auth.html
>
> * igt@fbdev@eof:
> - fi-kbl-8809g: NOTRUN -> [INCOMPLETE][12] ([i915#5557])
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22819/fi-kbl-8809g/
> igt@fb...@eof.html
>
> * igt@gem_close_race
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/uncore: Warn on previous unclaimed accesses
Those failures are directing towards
https://gitlab.freedesktop.org/drm/intel/-/issues/1436 which was closed long
back and I see the filters are also broken.
So, I have filed a new issue and new filter
https://gitlab.freedesktop.org/drm/intel/-/issues/5566
Thanks,
Lakshmi.
-Original Message-
From: De Marchi, Lucas
Sent: Tuesday, April 5, 2022 8:20 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/uncore: Warn on previous
unclaimed accesses
On Tue, Apr 05, 2022 at 09:43:58AM +, Patchwork wrote:
>== Series Details ==
>
>Series: drm/i915/uncore: Warn on previous unclaimed accesses
>URL : https://patchwork.freedesktop.org/series/102167/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_11452_full -> Patchwork_22778_full
>
>
>Summary
>---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22778_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22778_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
>
>
>Participating hosts (12 -> 13)
>--
>
> Additional (1): shard-dg1
>
>Possible new issues
>---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22778_full:
>
>### IGT changes ###
>
> Possible regressions
>
> * igt@gen9_exec_parse@allowed-all:
>- shard-skl: [PASS][1] -> [DMESG-WARN][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-skl1/igt@gen9_exec_pa...@allowed-all.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22778/shard-skl4/igt@gen9_exec_pa...@allowed-all.html
>- shard-apl: [PASS][3] -> [DMESG-WARN][4]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-apl4/igt@gen9_exec_pa...@allowed-all.html
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22778/shard-apl7/igt@gen9_exec_pa...@allowed-all.html
>- shard-glk: [PASS][5] -> [DMESG-WARN][6]
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-glk1/igt@gen9_exec_pa...@allowed-all.html
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22778/shard-glk8/igt@gen9_exec_pa...@allowed-all.html
>- shard-kbl: [PASS][7] -> [DMESG-WARN][8]
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-kbl6/igt@gen9_exec_pa...@allowed-all.html
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22778/shard-kbl7/ig
> t@gen9_exec_pa...@allowed-all.html
don't shoot the messenger :)
Lakshmi, these need to be mapped to previous failures. Here we are just
changing the message logged to make clear they aren't caused by the register we
are currently reading/writting, but it's rather cause by a previous read/write.
All of these should have a previous issue already with the different message,
not being caused by this patch.
Lucas De Marchi
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_pm_rpm@system-suspend-devices:
>- {shard-rkl}:[PASS][9] -> [FAIL][10]
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-rkl-1/igt@i915_pm_...@system-suspend-devices.html
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22778/shard-rkl-5/i
> gt@i915_pm_...@system-suspend-devices.html
>
>
>Known issues
>
>
> Here are the changes found in Patchwork_22778_full that come from known
> issues:
>
>### CI changes ###
>
> Issues hit
>
> * boot:
>- shard-skl: ([PASS][11], [PASS][12], [PASS][13], [PASS][14],
> [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20],
> [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26],
> [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31], [PASS][32],
> [PASS][33], [PASS][34], [PASS][35]) -> ([PASS][36], [PASS][37], [PASS][38],
> [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44],
> [PASS][45], [PASS][46], [FAIL][47], [PASS][48], [PASS][49], [PASS][50],
> [PASS][51], [PASS][52], [PASS][53], [PASS][54], [PASS][55], [PASS][56],
> [PASS][57]) ([i915#5032])
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-skl9/boot.html
> [12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11452/shard-skl9/boot.html
> [13]:
> https:/
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for lmem_size modparam
Filed a new issue for the regression
https://gitlab.freedesktop.org/drm/intel/-/issues/5435
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Friday, March 25, 2022 2:49 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for lmem_size modparam
On 24/03/2022 20:15, Patchwork wrote:
> *Patch Details*
> *Series:* lmem_size modparam
> *URL:*https://patchwork.freedesktop.org/series/101744/
> <https://patchwork.freedesktop.org/series/101744/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11402_full -> Patchwork_22671_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22671_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22671_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
>
> Participating hosts (11 -> 11)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22671_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@gem_exec_schedule@wide@vcs0:
> o shard-skl: NOTRUN -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-skl2/i
> gt@gem_exec_schedule@w...@vcs0.html>
Unrelated fail.
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_frontbuffer_tracking@fbc-tiling-4:
> o {shard-tglu}: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-tglu-2
> /igt@kms_frontbuffer_track...@fbc-tiling-4.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_22671_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@feature_discovery@psr2:
>
> o shard-iclb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-iclb7/igt@feature_discov...@psr2.html>
> ([i915#658])
> *
>
> igt@gem_ctx_persistence@engines-mixed:
>
> o shard-snb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-snb5/igt@gem_ctx_persiste...@engines-mixed.html>
> ([fdo#109271] / [i915#1099]) +1 similar issue
> *
>
> igt@gem_ctx_sseu@engines:
>
> o shard-tglb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-tglb3/igt@gem_ctx_s...@engines.html>
> ([i915#280])
> *
>
> igt@gem_eio@in-flight-suspend:
>
> o shard-kbl: NOTRUN -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-kbl4/igt@gem_...@in-flight-suspend.html>
> ([i915#3614])
> *
>
> igt@gem_eio@unwedge-stress:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11402/shard-iclb4/igt@gem_...@unwedge-stress.html>
> -> TIMEOUT
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-iclb3/igt@gem_...@unwedge-stress.html>
> ([i915#2481] / [i915#3070])
> *
>
> igt@gem_exec_balancer@parallel-bb-first:
>
> o
>
> shard-skl: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-skl9/igt@gem_exec_balan...@parallel-bb-first.html>
> ([fdo#109271] / [i915#1888])
>
> o
>
> shard-tglb: NOTRUN -> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-tglb5/igt@gem_exec_balan...@parallel-bb-first.html>
> ([i915#5076])
>
> o
>
> shard-kbl: NOTRUN -> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-kbl4/igt@gem_exec_balan...@parallel-bb-first.html>
> ([i915#5076])
>
> o
>
> shard-iclb: NOTRUN -> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22671/shard-iclb1/igt@gem_exec_balan...@parallel-bb-first.html>
> ([i915#5076])
>
> *
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: Extend DP HDR support to hsw+ (rev4)
Re-reported.
From: Shankar, Uma
Sent: Friday, March 25, 2022 3:35 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: RE: ✗ Fi.CI.IGT: failure for drm/i915/display: Extend DP HDR support
to hsw+ (rev4)
From: Patchwork
mailto:patchw...@emeril.freedesktop.org>>
Sent: Thursday, March 24, 2022 10:43 PM
To: Shankar, Uma mailto:uma.shan...@intel.com>>
Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Subject: ✗ Fi.CI.IGT: failure for drm/i915/display: Extend DP HDR support to
hsw+ (rev4)
Patch Details
Series:
drm/i915/display: Extend DP HDR support to hsw+ (rev4)
URL:
https://patchwork.freedesktop.org/series/101708/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/index.html
CI Bug Log - changes from CI_DRM_11401_full -> Patchwork_22670_full
Summary
FAILURE
Serious unknown changes coming with Patchwork_22670_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22670_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (11 -> 11)
No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_22670_full:
IGT changes
Possible regressions
* igt@i915_selftest@live@reset:
* shard-skl: NOTRUN ->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-skl4/igt@i915_selftest@l...@reset.html>
Hi Lakshmi,
This is not related to the change, can you help report it.
Thanks & Regards,
Uma Shankar
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@kms_frontbuffer_tracking@fbc-tiling-4:
* {shard-tglu}: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-tglu-2/igt@kms_frontbuffer_track...@fbc-tiling-4.html>
Known issues
Here are the changes found in Patchwork_22670_full that come from known issues:
IGT changes
Issues hit
* igt@feature_discovery@psr2:
* shard-iclb: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-iclb3/igt@feature_discov...@psr2.html>
([i915#658])
* igt@gem_eio@kms:
* shard-tglb:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11401/shard-tglb6/igt@gem_...@kms.html>
->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-tglb2/igt@gem_...@kms.html>
([i915#232])
* igt@gem_exec_balancer@parallel-balancer:
* shard-iclb:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11401/shard-iclb2/igt@gem_exec_balan...@parallel-balancer.html>
->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-iclb6/igt@gem_exec_balan...@parallel-balancer.html>
([i915#4525])
* igt@gem_exec_balancer@parallel-contexts:
* shard-tglb: NOTRUN ->
DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-tglb2/igt@gem_exec_balan...@parallel-contexts.html>
([i915#5076])
* igt@gem_exec_fair@basic-deadline:
* shard-skl: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-skl10/igt@gem_exec_f...@basic-deadline.html>
([i915#2846])
* igt@gem_exec_fair@basic-none-solo@rcs0:
* shard-tglb: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-tglb6/igt@gem_exec_fair@basic-none-s...@rcs0.html>
([i915#2842])
* igt@gem_exec_fair@basic-none-vip@rcs0:
* shard-kbl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11401/shard-kbl1/igt@gem_exec_fair@basic-none-...@rcs0.html>
->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-kbl6/igt@gem_exec_fair@basic-none-...@rcs0.html>
([i915#2842])
* shard-iclb: NOTRUN ->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-iclb3/igt@gem_exec_fair@basic-none-...@rcs0.html>
([i915#2842]) +2 similar issues
* igt@gem_exec_fair@basic-pace-share@rcs0:
* shard-tglb:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11401/shard-tglb8/igt@gem_exec_fair@basic-pace-sh...@rcs0.html>
->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-tglb3/igt@gem_exec_fair@basic-pace-sh...@rcs0.html>
([i915#2842])
* igt@gem_lmem_swapping@basic:
* shard-iclb: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-iclb3/igt@gem_lmem_swapp...@basic.html>
([i915#4613])
* igt@gem_lmem_swapping@parallel-multi:
* shard-kbl: NOTRUN ->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22670/shard-kbl3/igt@gem_lmem_swapp...@parallel-multi.html>
([fdo#109271] / [i915#4613])
* igt@gem_lmem_swapping@random
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Remove check for ComboPHY I/O voltage for DP source rate (rev5)
Filed a new issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/5436
igt@gem_exec_whisper@basic-fds-(forked|priority)-all - incomplete - general
protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7c33
From: Nautiyal, Ankit K
Sent: Friday, March 25, 2022 2:50 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: RE: ✗ Fi.CI.IGT: failure for Remove check for ComboPHY I/O voltage for
DP source rate (rev5)
Hello Lakshmi,
The below regressions are known issue and are not related patches:
* igt@gem_exec_whisper@basic-fds-forked-all:
* shard-kbl: NOTRUN ->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-kbl1/igt@gem_exec_whis...@basic-fds-forked-all.html>
https://gitlab.freedesktop.org/drm/intel/-/issues/5268
* igt@gem_exec_whisper@basic-fds-priority-all:
* shard-skl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-skl1/igt@gem_exec_whis...@basic-fds-priority-all.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-skl6/igt@gem_exec_whis...@basic-fds-priority-all.html>
https://gitlab.freedesktop.org/drm/intel/-/issues/5268
* igt@perf@enable-disable:
* shard-skl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-skl2/igt@p...@enable-disable.html>
->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-skl10/igt@p...@enable-disable.html>
[https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11396/shard-skl5/igt@p...@enable-disable.html
https://gitlab.freedesktop.org/drm/intel/-/issues/1352]
Regards,
Ankit
From: Patchwork
mailto:patchw...@emeril.freedesktop.org>>
Sent: Wednesday, March 23, 2022 7:40 PM
To: Nautiyal, Ankit K
mailto:ankit.k.nauti...@intel.com>>
Cc: intel-gfx@lists.freedesktop.org<mailto:intel-gfx@lists.freedesktop.org>
Subject: ✗ Fi.CI.IGT: failure for Remove check for ComboPHY I/O voltage for DP
source rate (rev5)
Patch Details
Series:
Remove check for ComboPHY I/O voltage for DP source rate (rev5)
URL:
https://patchwork.freedesktop.org/series/96293/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/index.html
CI Bug Log - changes from CI_DRM_11398_full -> Patchwork_22655_full
Summary
FAILURE
Serious unknown changes coming with Patchwork_22655_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22655_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (12 -> 12)
No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_22655_full:
IGT changes
Possible regressions
* igt@gem_exec_whisper@basic-fds-forked-all:
* shard-kbl: NOTRUN ->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-kbl1/igt@gem_exec_whis...@basic-fds-forked-all.html>
* igt@gem_exec_whisper@basic-fds-priority-all:
* shard-skl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-skl1/igt@gem_exec_whis...@basic-fds-priority-all.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-skl6/igt@gem_exec_whis...@basic-fds-priority-all.html>
* igt@perf@enable-disable:
* shard-skl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-skl2/igt@p...@enable-disable.html>
->
FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-skl10/igt@p...@enable-disable.html>
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_workarounds@suspend-resume-context:
* {shard-rkl}:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-rkl-1/igt@gem_workarou...@suspend-resume-context.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-rkl-5/igt@gem_workarou...@suspend-resume-context.html>
Known issues
Here are the changes found in Patchwork_22655_full that come from known issues:
IGT changes
Issues hit
* igt@gem_exec_balancer@parallel-balancer:
* shard-iclb:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-iclb4/igt@gem_exec_balan...@parallel-balancer.html>
->
SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-iclb5/igt@gem_exec_balan...@parallel-balancer.html>
([i915#4525])
* igt@gem_exec_capture@pi@rcs0:
* shard-skl:
PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11398/shard-skl2/igt@gem_exec_capture@p...@rcs0.html>
->
INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22655/shard-skl9/igt@gem_exec_capture@p...@rcs0.html>
([i915#4547])
* igt@gem_exec_fair@basic-deadline
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS (rev2)
Regression on RKL is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/4418
Thanks,
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Friday, March 25, 2022 2:49 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/ttm:
limit where we apply TTM_PL_FLAG_CONTIGUOUS (rev2)
On 25/03/2022 09:22, Patchwork wrote:
> *Patch Details*
> *Series:* series starting with [1/2] drm/i915/ttm: limit where we apply
> TTM_PL_FLAG_CONTIGUOUS (rev2)
> *URL:*https://patchwork.freedesktop.org/series/101749/
> <https://patchwork.freedesktop.org/series/101749/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11403 -> Patchwork_22677
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22677 absolutely need to
> be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22677, please notify your bug team 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_22677/index.html
>
>
> Participating hosts (44 -> 40)
>
> Missing (4): fi-bsw-cyan shard-rkl shard-tglu fi-bdw-samus
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22677:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@i915_selftest@live@gt_engines:
> o fi-rkl-guc: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11403/fi-rkl-guc/igt@i915_selftest@live@gt_engines.html>
> -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/fi-rkl-guc/i
> gt@i915_selftest@live@gt_engines.html>
Unrelated fail.
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_selftest@live@uncore:
> o {bat-rpls-2}: NOTRUN -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/bat-rpls-2/i
> gt@i915_selftest@l...@uncore.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_22677 that come from known issues:
>
>
> IGT changes
>
>
> Issues hit
>
> * igt@runner@aborted:
> o fi-rkl-guc: NOTRUN -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/fi-rkl-guc/igt@run...@aborted.html>
> (i915#4312
> <https://gitlab.freedesktop.org/drm/intel/issues/4312>)
>
>
> Possible fixes
>
> *
>
> igt@i915_module_load@reload:
>
> o {bat-rpls-2}: DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11403/bat-rpls-2/igt@i915_module_l...@reload.html>
> (i915#4391
> <https://gitlab.freedesktop.org/drm/intel/issues/4391>) -> PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/bat-rpls-2/igt@i915_module_l...@reload.html>
> *
>
> igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
>
> o fi-cfl-8109u: DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11403/fi-cfl-8109u/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-b.html>
> (i915#295 <https://gitlab.freedesktop.org/drm/intel/issues/295>)
> -> PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/fi-cfl-8109u/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-b.html>
> +10 similar issues
> *
>
> igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
>
> o fi-cfl-8109u: DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11403/fi-cfl-8109u/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html>
> (i915#295 <https://gitlab.freedesktop.org/drm/intel/issues/295>
> / i915#5341
> <https://gitlab.freedesktop.org/drm/intel/issues/5341>) -> PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22677/fi-cfl-8109u
> /igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html>
>
> {name}: This element is suppressed. This means it is ignored when
> computing the status of the difference (SUCCESS, WARNING, or FAILURE).
>
>
> Build changes
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: Add smem fallback allocation for dpt
Below one looks like a new issue
https://gitlab.freedesktop.org/drm/intel/-/issues/5386
igt@perf@stress-open-close - dmesg-fail - general protection fault, probably
for non-canonical address 0x6b6b6b6b6b6b6bcb, RIP: 0010:i915_oa_init_reg_state
Thanks,
Lakshmi.
-Original Message-
From: Juha-Pekka Heikkila
Sent: Monday, March 21, 2022 1:28 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/display: Add smem fallback
allocation for dpt
Hi Lakshmi,
here would be again false positive on glk, glk doesn't use dpt which is changed
on my patch.
/Juha-Pekka
On 17.3.2022 4.31, Patchwork wrote:
> *Patch Details*
> *Series:* drm/i915/display: Add smem fallback allocation for dpt
> *URL:*https://patchwork.freedesktop.org/series/101443/
> <https://patchwork.freedesktop.org/series/101443/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11372_full -> Patchwork_22588_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22588_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22588_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
>
> Participating hosts (11 -> 12)
>
> Additional (1): shard-rkl
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22588_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@perf@stress-open-close:
> o shard-glk: NOTRUN -> DMESG-FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-glk2/i
> gt@p...@stress-open-close.html>
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@i915_pm_dc@dc5-dpms:
> o {shard-rkl}: NOTRUN -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-rkl-5/
> igt@i915_pm...@dc5-dpms.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_22588_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_eio@kms:
>
> o shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-tglb7/igt@gem_...@kms.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-tglb8/igt@gem_...@kms.html>
> ([i915#232])
> *
>
> igt@gem_exec_balancer@parallel-balancer:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-iclb2/igt@gem_exec_balan...@parallel-balancer.html>
> -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-iclb3/igt@gem_exec_balan...@parallel-balancer.html>
> ([i915#4525])
> *
>
> igt@gem_exec_capture@pi@rcs0:
>
> o shard-skl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-skl10/igt@gem_exec_capture@p...@rcs0.html>
> -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-skl7/igt@gem_exec_capture@p...@rcs0.html>
> ([i915#4547])
> *
>
> igt@gem_exec_endless@dispatch@vecs0:
>
> o shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-tglb6/igt@gem_exec_endless@dispa...@vecs0.html>
> -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-tglb5/igt@gem_exec_endless@dispa...@vecs0.html>
> ([i915#3778])
> *
>
> igt@gem_exec_fair@basic-none-share@rcs0:
>
> o
>
> shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-iclb2/igt@gem_exec_fair@basic-none-sh...@rcs0.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22588/shard-iclb6/igt@gem_exec_fair@basic-none-sh...@rcs0.html>
> ([i915#2842])
>
> o
>
> shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-tglb6/igt@gem_exec_fair@basic-none-sh...
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Introduce multitile support
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/1373 Few tests - incomplete - Kernel panic - not syncing: EXT4-fs (device nvme0n1p2): panic forced after error|Kernel panic - not syncing: EXT4-fs panic from previous error Lakshmi. -Original Message- From: Matthew Auld Sent: Monday, March 21, 2022 3:05 AM To: Intel Graphics Development ; Vudum, Lakshminarayana Cc: Andi Shyti Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Introduce multitile support On Sat, 19 Mar 2022 at 02:06, Patchwork wrote: > > Patch Details > Series:Introduce multitile support > URL:https://patchwork.freedesktop.org/series/101551/ > State:failure > Details:https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22617/index > .html > > CI Bug Log - changes from CI_DRM_11384_full -> Patchwork_22617_full > > Summary > > FAILURE > > Serious unknown changes coming with Patchwork_22617_full absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_22617_full, please notify your bug team to > allow them to document this new failure mode, which will reduce false > positives in CI. > > Participating hosts (12 -> 12) > > No changes in participating hosts > > Possible new issues > > Here are the unknown changes that may have been introduced in > Patchwork_22617_full: > > IGT changes > > Possible regressions > > igt@gem_workarounds@suspend-resume: > > shard-kbl: PASS -> INCOMPLETE Unrelated failure. Looks like filesystem related issue: <4>[ 122.379815] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:346: I/O error 10 writing to inode 27001858 starting block 13317428) <6>[ 122.379827] nvme0n1: detected capacity change from 1000215216 to 0 <3>[ 122.379933] Buffer I/O error on device nvme0n1p2, logical block 13186100 <2>[ 122.380063] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1614: inode #24510583: comm systemd-udevd: reading directory lblock 0 <3>[ 122.380358] Aborting journal on device nvme0n1p2-8. <2>[ 122.380488] EXT4-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5706: Journal has aborted <2>[ 122.380612] EXT4-fs error (device nvme0n1p2): ext4_journal_check_start:83: comm dmesg: Detected aborted journal <3>[ 122.380671] Buffer I/O error on dev nvme0n1p2, logical block 62423040, lost sync page write <3>[ 122.380721] JBD2: Error -5 detected when updating journal superblock for nvme0n1p2-8. <2>[ 122.380935] EXT4-fs error (device nvme0n1p2): ext4_journal_check_start:83: comm rs:main Q:Reg: Detected aborted journal <4>[ 122.381311] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <4>[ 122.381428] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <4>[ 122.381517] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <4>[ 122.381588] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <4>[ 122.381659] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <3>[ 122.381728] Buffer I/O error on dev nvme0n1p2, logical block 0, lost sync page write <4>[ 122.381734] EXT4-fs warning (device nvme0n1p2): dx_probe:788: inode #3539533: lblock 0: comm systemd: error -5 reading directory block <3>[ 122.381741] EXT4-fs (nvme0n1p2): I/O error while writing superblock <0>[ 122.381744] Kernel panic - not syncing: EXT4-fs (device nvme0n1p2): panic forced after error <0>[ 122.381750] Kernel Offset: disabled <4>[ 122.381762] CPU: 2 PID: 378 Comm: rs:main Q:Reg Not tainted 5.17.0-rc8-CI-Patchwork_22617+ #1 <4>[ 122.381766] Hardware name: /NUC7i5BNB, BIOS BNKBL357.86A.0083.2020.0714.1344 07/14/2020 <4>[ 122.381771] Call Trace: <4>[ 122.381775] <4>[ 122.381777] dump_stack_lvl+0x56/0x7b <4>[ 122.381783] panic+0x12a/0x2c3 <4>[ 122.381794] ext4_handle_error.cold.167+0x13/0x13 <4>[ 122.381801] __ext4_error+0x104/0x1f0 <4>[ 122.381819] ext4_journal_check_start+0x84/0xa0 <4>[ 122.381823] __ext4_journal_start_sb+0x41/0x180 <4>[ 122.381829] ext4_dirty_inode+0x2f/0x70 <4>[ 122.381833] __mark_inode_dirty+0x181/0x580 <4>[ 122.381838] generic_update_time+0x98/0xc0 <4>[ 122.381842] file_update_time+0xc3/0x110 <4>[ 122.381844] ? generic_write_checks+0x5c/0xc0 <4>[ 122.381851] ext4_buffered_write_iter+0x4b/0x100 <4>[ 122.381858] ext4_file_write_iter+0x5a/0x830 <4>[ 122.38
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: Add preemption changes for Wa_14015141709 (rev2)
Yes, I have re-opened the issue #3812 and re-reported.
-Original Message-
From: Roper, Matthew D
Sent: Friday, March 18, 2022 10:21 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/dg2: Add preemption changes for
Wa_14015141709 (rev2)
On Fri, Mar 18, 2022 at 04:51:14AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dg2: Add preemption changes for Wa_14015141709 (rev2)
> URL : https://patchwork.freedesktop.org/series/101023/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11379_full -> Patchwork_22602_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22602_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22602_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (12 -> 12)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22602_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_exec_parallel@engines@contexts:
> - shard-iclb: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-iclb7/igt@gem_exec_parallel@engi...@contexts.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-iclb4/i
> gt@gem_exec_parallel@engi...@contexts.html
>
Unexpected incomplete with no apparent warnings/errors. Looks like we
previously had https://gitlab.freedesktop.org/drm/intel/-/issues/3812
open for this but it wasn't seen for a while and got closed.
This patch doesn't change the behavior of ICL, so it shouldn't be the cause.
Patch applied to drm-intel-gt-next. Thanks Anusha for the review.
Matt
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_parallel@fds@vecs0:
> - {shard-rkl}:([PASS][3], [PASS][4]) -> [INCOMPLETE][5]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-rkl-4/igt@gem_exec_parallel@f...@vecs0.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-rkl-5/igt@gem_exec_parallel@f...@vecs0.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-rkl-5/i
> gt@gem_exec_parallel@f...@vecs0.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22602_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_create@create-massive:
> - shard-apl: NOTRUN -> [DMESG-WARN][6] ([i915#4991])
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-apl8/ig
> t@gem_cre...@create-massive.html
>
> * igt@gem_eio@kms:
> - shard-tglb: [PASS][7] -> [FAIL][8] ([i915#232])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-tglb6/igt@gem_...@kms.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-tglb1/i
> gt@gem_...@kms.html
>
> * igt@gem_exec_capture@pi@bcs0:
> - shard-skl: NOTRUN -> [INCOMPLETE][9] ([i915#4547])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-skl6/ig
> t@gem_exec_capture@p...@bcs0.html
>
> * igt@gem_exec_fair@basic-none-rrul@rcs0:
> - shard-iclb: NOTRUN -> [FAIL][10] ([i915#2842])
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-iclb3/i
> gt@gem_exec_fair@basic-none-r...@rcs0.html
>
> * igt@gem_exec_fair@basic-none@vcs0:
> - shard-kbl: [PASS][11] -> [FAIL][12] ([i915#2842]) +1 similar
> issue
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-kbl3/igt@gem_exec_fair@basic-n...@vcs0.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22602/shard-kbl4/ig
> t@gem_exec_fair@basic-n...@vcs0.html
>
> * igt@gem_exec_fair@basic-pace-share@rcs0:
> - shard-tglb: [PASS][13] -> [FAIL][14] ([i915#2842])
>[13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11379/shard-tglb6/igt@gem_exec_fair@basic-pace-sh...@rcs0.html
>[14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_2
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Fix renamed struct field
Regression is related to https://gitlab.freedesktop.org/drm/intel/-/issues/4391 All tests - dmesg-warn/dmesg-fail - *ERROR* AUX B/DDI B/PHY B: did not complete or timeout within 10ms (status 0xad4003ff) Re-reported the results. Lakshmi. -Original Message- From: De Marchi, Lucas Sent: Friday, March 18, 2022 7:52 AM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Fix renamed struct field On Thu, Mar 17, 2022 at 04:14:16AM +, Patchwork wrote: >== Series Details == > >Series: series starting with [1/2] drm/i915: Fix renamed struct field >URL : https://patchwork.freedesktop.org/series/101448/ >State : failure > >== Summary == > >CI Bug Log - changes from CI_DRM_11372_full -> Patchwork_22590_full > > >Summary >--- > > **FAILURE** > > Serious unknown changes coming with Patchwork_22590_full absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_22590_full, please notify your bug team to > allow them to document this new failure mode, which will reduce false > positives in CI. > > > >Participating hosts (11 -> 11) >-- > > No changes in participating hosts > >Possible new issues >--- > > Here are the unknown changes that may have been introduced in > Patchwork_22590_full: > >### IGT changes ### > > Possible regressions > > * igt@gem_mmap_wc@write-wc-read-gtt: >- shard-skl: [PASS][1] -> [INCOMPLETE][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-skl9/igt@gem_mmap...@write-wc-read-gtt.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-skl6/ig > t@gem_mmap...@write-wc-read-gtt.html nothing related to this series that only changes the behavior for media engine on media_ver >= 11 Lucas De Marchi > > >Known issues > > > Here are the changes found in Patchwork_22590_full that come from known > issues: > >### IGT changes ### > > Issues hit > > * igt@gem_ctx_isolation@preservation-s3@vcs0: >- shard-kbl: [PASS][3] -> [DMESG-WARN][4] ([i915#180]) +3 similar > issues > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-kbl1/igt@gem_ctx_isolation@preservation...@vcs0.html > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-kbl7/ig > t@gem_ctx_isolation@preservation...@vcs0.html > > * igt@gem_exec_capture@pi@rcs0: >- shard-skl: [PASS][5] -> [INCOMPLETE][6] ([i915#4547]) > [5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-skl10/igt@gem_exec_capture@p...@rcs0.html > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-skl4/ig > t@gem_exec_capture@p...@rcs0.html > > * igt@gem_exec_fair@basic-none@vcs0: >- shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2842]) +2 similar > issues > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-kbl1/igt@gem_exec_fair@basic-n...@vcs0.html > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-kbl3/ig > t@gem_exec_fair@basic-n...@vcs0.html > > * igt@gem_exec_fair@basic-pace-share@rcs0: >- shard-tglb: [PASS][9] -> [FAIL][10] ([i915#2842]) > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-tglb5/igt@gem_exec_fair@basic-pace-sh...@rcs0.html > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-tglb5/i > gt@gem_exec_fair@basic-pace-sh...@rcs0.html > > * igt@gem_exec_fair@basic-pace-solo@rcs0: >- shard-glk: NOTRUN -> [FAIL][11] ([i915#2842]) +1 similar issue > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-glk9/ig > t@gem_exec_fair@basic-pace-s...@rcs0.html > > * igt@gem_exec_fair@basic-throttle@rcs0: >- shard-glk: [PASS][12] -> [FAIL][13] ([i915#2842]) > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-glk5/igt@gem_exec_fair@basic-throt...@rcs0.html > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-glk3/ig > t@gem_exec_fair@basic-throt...@rcs0.html > > * igt@gem_exec_suspend@basic-s3@smem: >- shard-apl: [PASS][14] -> [DMESG-WARN][15] ([i915#180]) +4 > similar issues > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11372/shard-apl2/igt@gem_exec_suspend@basic...@smem.html > [15]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22590/shard-apl3/ig > t@gem_exec_suspe
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/7] drm/i915/lmem: don't treat small BAR as an error
I have re-opened this issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/2995
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Wednesday, March 16, 2022 2:15 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [CI,1/7]
drm/i915/lmem: don't treat small BAR as an error
On 16/03/2022 00:38, Patchwork wrote:
> *Patch Details*
> *Series:* series starting with [CI,1/7] drm/i915/lmem: don't treat small
> BAR as an error
> *URL:*https://patchwork.freedesktop.org/series/101398/
> <https://patchwork.freedesktop.org/series/101398/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11365_full -> Patchwork_22576_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22576_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22576_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 -> 13)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22576_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_sequence@queue-busy:
> o shard-skl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shard-skl1/igt@kms_seque...@queue-busy.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-skl3/i
> gt@kms_seque...@queue-busy.html>
Looks to be unrelated.
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> *
>
> igt@gem_ccs@block-copy-inplace:
>
> o {shard-dg1}: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-dg1-12/igt@gem_...@block-copy-inplace.html>
> *
>
> igt@gem_eio@in-flight-suspend:
>
> o {shard-rkl}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shard-rkl-1/igt@gem_...@in-flight-suspend.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-rkl-4/
> igt@gem_...@in-flight-suspend.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_22576_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@feature_discovery@chamelium:
>
> o shard-iclb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-iclb2/igt@feature_discov...@chamelium.html>
> ([fdo#111827])
> *
>
> igt@gem_eio@unwedge-stress:
>
> o
>
> shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shard-tglb7/igt@gem_...@unwedge-stress.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-tglb8/igt@gem_...@unwedge-stress.html>
> ([i915#232])
>
> o
>
> shard-skl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shard-skl4/igt@gem_...@unwedge-stress.html>
> -> TIMEOUT
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-skl7/igt@gem_...@unwedge-stress.html>
> ([i915#3063])
>
> *
>
> igt@gem_exec_fair@basic-deadline:
>
> o shard-skl: NOTRUN -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-skl3/igt@gem_exec_f...@basic-deadline.html>
> ([i915#2846])
> *
>
> igt@gem_exec_fair@basic-none-vip@rcs0:
>
> o shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shard-tglb6/igt@gem_exec_fair@basic-none-...@rcs0.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22576/shard-tglb3/igt@gem_exec_fair@basic-none-...@rcs0.html>
> ([i915#2842])
> *
>
> igt@gem_exec_fair@basic-none@vecs0:
>
> o shard-apl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11365/shar
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Some more bits for small BAR enabling (rev4)
Filed https://gitlab.freedesktop.org/drm/intel/-/issues/5349
igt@kms_cursor_legacy@pipe-b-torture-bo - incomplete - No warnings/errors
Thanks,
Lakshmi.
-Original Message-
From: Matthew Auld
Sent: Tuesday, March 15, 2022 5:37 AM
To: Intel Graphics Development ; Vudum,
Lakshminarayana
Cc: Auld, Matthew
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Some more bits for small BAR
enabling (rev4)
On Mon, 14 Mar 2022 at 16:49, Patchwork
wrote:
>
> Patch Details
> Series:Some more bits for small BAR enabling (rev4)
> URL:https://patchwork.freedesktop.org/series/101052/
> State:failure
> Details:https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22555/index
> .html
>
> CI Bug Log - changes from CI_DRM_11358_full -> Patchwork_22555_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_22555_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22555_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
> Participating hosts (12 -> 12)
>
> No changes in participating hosts
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22555_full:
>
> IGT changes
>
> Possible regressions
>
> igt@kms_cursor_legacy@pipe-b-torture-bo:
>
> shard-glk: PASS -> INCOMPLETE
Fairly sure this is unrelated. Realistically this series should only really
change things for discrete.
>
> Known issues
>
> Here are the changes found in Patchwork_22555_full that come from known
> issues:
>
> CI changes
>
> Possible fixes
>
> boot:
>
> shard-glk: (PASS, PASS, PASS, PASS, PASS, PASS, FAIL, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS) ([i915#4392]) -> (PASS, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS)
>
> {shard-rkl}: (PASS, PASS, FAIL, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS) ([i915#5131]) -> (PASS, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS, PASS,
> PASS, PASS)
>
> IGT changes
>
> Issues hit
>
> igt@gem_ccs@block-copy-compressed:
>
> shard-tglb: NOTRUN -> SKIP ([i915#5325])
>
> shard-iclb: NOTRUN -> SKIP ([i915#5327])
>
> igt@gem_create@create-massive:
>
> shard-iclb: NOTRUN -> DMESG-WARN ([i915#4991]) +1 similar issue
>
> igt@gem_exec_balancer@parallel-contexts:
>
> shard-kbl: NOTRUN -> DMESG-WARN ([i915#5076])
>
> igt@gem_exec_fair@basic-none-share@rcs0:
>
> shard-iclb: PASS -> FAIL ([i915#2842])
>
> igt@gem_huc_copy@huc-copy:
>
> shard-tglb: PASS -> SKIP ([i915#2190])
>
> igt@gem_lmem_swapping@heavy-verify-multi:
>
> shard-kbl: NOTRUN -> SKIP ([fdo#109271] / [i915#4613])
>
> shard-apl: NOTRUN -> SKIP ([fdo#109271] / [i915#4613])
>
> igt@gem_lmem_swapping@random-engines:
>
> shard-iclb: NOTRUN -> SKIP ([i915#4613]) +1 similar issue
>
> igt@gem_lmem_swapping@verify-random:
>
> shard-skl: NOTRUN -> SKIP ([fdo#109271] / [i915#4613]) +1 similar
> issue
>
> igt@gem_pxp@create-protected-buffer:
>
> shard-iclb: NOTRUN -> SKIP ([i915#4270]) +1 similar issue
>
> igt@gem_pxp@verify-pxp-stale-ctx-execution:
>
> shard-tglb: NOTRUN -> SKIP ([i915#4270])
>
> igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs:
>
> shard-iclb: NOTRUN -> SKIP ([i915#768]) +2 similar issues
>
> igt@gem_userptr_blits@unsync-overlap:
>
> shard-iclb: NOTRUN -> SKIP ([i915#3297]) +1 similar issue
>
> igt@gen7_exec_parse@basic-offset:
>
> shard-tglb: NOTRUN -> SKIP ([fdo#109289])
>
> igt@gen7_exec_parse@chained-batch:
>
> shard-iclb: NOTRUN -> SKIP ([fdo#109289]) +3 similar issues
>
> igt@gen9_exec_parse@allowed-single:
>
> shard-skl: PASS -> DMESG-WARN ([i915#1436] / [i915#716])
>
> igt@gen9_exec_parse@batch-without-end:
>
> shard-iclb: NOTRUN -> SKIP ([i915#2856]) +1 similar issue
>
> igt@i915_pm_dc@dc6-psr:
>
> shard-iclb: PASS -> FAIL ([i915#454])
>
> igt@i915_pm_rpm@dpms-mode-unset-non-lpsp:
>
> shard-iclb: NOTRUN -> SKIP ([fdo#110892])
>
> igt@i915_suspend@fence-restore-untiled:
>
> shard-kbl: PASS -> DMESG-WARN ([i915#180])
>
> igt@kms_addfb_basic@invalid-smem-bo-on-discrete:
>
> shard-iclb: NOTRUN -> SKIP ([i915#3826])
>
> igt@kms_big_fb@4-tiled-32bpp-rotate-270:
>
> shard-i
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Reduce stack usage in debugfs due to SSEU
Issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/3576
[ADL-P] KMS tests - dmesg-warn/dmesg-fail - *ERROR* CPU pipe A FIFO underrun:
(port|soft),transcoder,
And the latest reg from rev 2 is
https://gitlab.freedesktop.org/drm/intel/-/issues/5343
igt@i915_pm_dc@dc5-psr - crash - Received signal SIGSEGV.
Thanks,
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Monday, March 14, 2022 9:34 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Reduce stack usage in debugfs
due to SSEU
On Tue, Mar 15, 2022 at 03:01:44AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Reduce stack usage in debugfs due to SSEU
> URL : https://patchwork.freedesktop.org/series/101369/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11363 -> Patchwork_22566
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22566 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22566, please notify your bug team 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_22566/index.html
>
> Participating hosts (50 -> 43)
> --
>
> Additional (3): bat-adlm-1 bat-adlp-4 fi-kbl-8809g
> Missing(10): shard-tglu fi-hsw-4200u shard-rkl fi-icl-u2 fi-bsw-cyan
> fi-kbl-7500u fi-ctg-p8600 fi-hsw-4770 bat-rpls-2 fi-bdw-samus
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22566:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@kms_flip@basic-flip-vs-modeset@a-edp1:
> - bat-adlp-4: NOTRUN -> [DMESG-WARN][1]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/bat-adlp-4/ig
> t@kms_flip@basic-flip-vs-mode...@a-edp1.html
<3> [273.206566] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun:
port,transcoder,
A display underrun wouldn't be related to how a debugfs file (which isn't being
used here) allocates memory.
It seems like there are also a bunch of missing machines listed above for no
apparent reason. Submitting a re-test.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_busy@basic@flip:
> - {bat-adlp-6}: [PASS][2] -> [DMESG-WARN][3]
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11363/bat-adlp-6/igt@kms_busy@ba...@flip.html
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/bat-adlp-6/ig
> t@kms_busy@ba...@flip.html
>
> * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
> - {bat-dg2-9}:[DMESG-WARN][4] ([i915#5193]) -> [DMESG-FAIL][5]
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11363/bat-dg2-9/igt@kms_pipe_crc_ba...@suspend-read-crc-pipe-a.html
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/bat-dg2-9/igt
> @kms_pipe_crc_ba...@suspend-read-crc-pipe-a.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22566 that come from known issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_exec_suspend@basic-s0@smem:
> - fi-kbl-8809g: NOTRUN -> [DMESG-WARN][6] ([i915#4962]) +1 similar
> issue
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/fi-kbl-8809g/
> igt@gem_exec_suspend@basic...@smem.html
>
> * igt@gem_huc_copy@huc-copy:
> - fi-kbl-8809g: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#2190])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/fi-kbl-8809g/
> igt@gem_huc_c...@huc-copy.html
>
> * igt@gem_lmem_swapping@basic:
> - bat-adlp-4: NOTRUN -> [SKIP][8] ([i915#4613]) +3 similar issues
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/bat-adlp-4/ig
> t@gem_lmem_swapp...@basic.html
>
> * igt@gem_lmem_swapping@random-engines:
> - fi-kbl-8809g: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#4613]) +3
> similar issues
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22566/fi-kbl-8809g/
> igt@gem_lmem_swapp...@random-engines.html
>
> * igt@gem_tiled_pread_basic:
> - bat-adlp-4: NOTRUN -> [SKIP][10] ([i915#3282])
>[10]:
> https://intel-gfx-ci
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2)
From: Matthew Auld Sent: Thursday, March 10, 2022 1:21 AM To: Intel Graphics Development ; Vudum, Lakshminarayana Cc: Katragadda, MastanX Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2) On Thu, 3 Mar 2022 at 06:48, Patchwork mailto:patchw...@emeril.freedesktop.org>> wrote: Patch Details Series: drm/i915/gem: missing boundary check in vm_access leads to OOB read/write (rev2) URL: https://patchwork.freedesktop.org/series/100932/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/index.html CI Bug Log - changes from CI_DRM_11316 -> Patchwork_22468 Summary FAILURE Serious unknown changes coming with Patchwork_22468 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_22468, please notify your bug team 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_22468/index.html Participating hosts (50 -> 41) Additional (1): bat-adlp-4 Missing (10): fi-kbl-soraka shard-tglu bat-dg1-5 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 shard-rkl shard-dg1 bat-jsl-2 fi-bdw-samus Possible new issues Here are the unknown changes that may have been introduced in Patchwork_22468: IGT changes Possible regressions * igt@gem_exec_suspend@basic-s0@smem: * fi-kbl-7567u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-kbl-7567u/igt@gem_exec_suspend@basic...@smem.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-kbl-7567u/igt@gem_exec_suspend@basic...@smem.html> Lakshmi: This issue is related to https://gitlab.freedesktop.org/drm/intel/-/issues/4116 * igt@i915_pm_rpm@basic-pci-d3-state: * fi-skl-6600u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11316/fi-skl-6600u/igt@i915_pm_...@basic-pci-d3-state.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/fi-skl-6600u/igt@i915_pm_...@basic-pci-d3-state.html> Lakshmi: This looks like a new issue, so filed https://gitlab.freedesktop.org/drm/intel/-/issues/5290 igt@i915_pm_rpm@basic-pci-d3-state - fail - Failed assertion: igt_wait(device_in_pci_d3(), \d+, \d+) These failures are not related. * Known issues Here are the changes found in Patchwork_22468 that come from known issues: IGT changes Issues hit * igt@gem_lmem_swapping@basic: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@gem_lmem_swapp...@basic.html> (i915#4613<https://gitlab.freedesktop.org/drm/intel/issues/4613>) +3 similar issues * igt@gem_tiled_pread_basic: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@gem_tiled_pread_basic.html> (i915#3282<https://gitlab.freedesktop.org/drm/intel/issues/3282>) * igt@kms_busy@basic@modeset: * bat-adlp-4: NOTRUN -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_busy@ba...@modeset.html> (i915#3576<https://gitlab.freedesktop.org/drm/intel/issues/3576>) * igt@kms_chamelium@vga-hpd-fast: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_chamel...@vga-hpd-fast.html> (fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 similar issues * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-legacy.html> (i915#4103<https://gitlab.freedesktop.org/drm/intel/issues/4103>) +1 similar issue * igt@kms_force_connector_basic@force-load-detect: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@kms_force_connector_ba...@force-load-detect.html> (fdo#109285<https://bugs.freedesktop.org/show_bug.cgi?id=109285>) * igt@prime_vgem@basic-fence-read: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@prime_v...@basic-fence-read.html> (i915#3291<https://gitlab.freedesktop.org/drm/intel/issues/3291> / i915#3708<https://gitlab.freedesktop.org/drm/intel/issues/3708>) +2 similar issues * igt@prime_vgem@basic-userptr: * bat-adlp-4: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22468/bat-adlp-4/igt@prime_v...@basic-userptr.html> (i915#3301<https://gitlab.freedesktop.org/drm/intel/issues/3301> / i915#3708<https://gitlab.freedesktop.org/drm/intel/issues/3708>) * igt@runner@aborted: * fi-kbl-7567u: NOTRUN -> FAIL&
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: opportunistically apply ALLOC_CONTIGIOUS (rev2)
Filed a new issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/5267
igt@kms_plane@plane-position-hole@pipe-b-planes - incomplete - No
warnings/errors
Thanks,
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Tuesday, March 8, 2022 4:26 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: opportunistically apply
ALLOC_CONTIGIOUS (rev2)
On 07/03/2022 17:52, Patchwork wrote:
> *Patch Details*
> *Series:* drm/i915: opportunistically apply ALLOC_CONTIGIOUS (rev2)
> *URL:*https://patchwork.freedesktop.org/series/99631/
> <https://patchwork.freedesktop.org/series/99631/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11332_full -> Patchwork_22498_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22498_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22498_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 -> 13)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22498_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_plane@plane-position-hole@pipe-b-planes:
> o shard-tglb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11332/shard-tglb3/igt@kms_plane@plane-position-h...@pipe-b-planes.html>
> -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-tglb8/
> igt@kms_plane@plane-position-h...@pipe-b-planes.html>
>
>
Unrelated failure. Patch only has potential impact of dgpu.
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_parallel@contexts@vecs0:
> o {shard-rkl}: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11332/shard-rkl-2/igt@gem_exec_parallel@conte...@vecs0.html>
> -> (PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-rkl-4/igt@gem_exec_parallel@conte...@vecs0.html>,
> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-rkl-5/igt@gem_exec_parallel@conte...@vecs0.html>)
> +1 similar issue
>
>
> Known issues
>
> Here are the changes found in Patchwork_22498_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@feature_discovery@display-3x:
>
> o shard-glk: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-glk6/igt@feature_discov...@display-3x.html>
> ([fdo#109271]) +40 similar issues
> *
>
> igt@gem_eio@unwedge-stress:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11332/shard-iclb7/igt@gem_...@unwedge-stress.html>
> -> TIMEOUT
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-iclb7/igt@gem_...@unwedge-stress.html>
> ([i915#2481] / [i915#3070])
> *
>
> igt@gem_exec_balancer@parallel-balancer:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11332/shard-iclb1/igt@gem_exec_balan...@parallel-balancer.html>
> -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-iclb3/igt@gem_exec_balan...@parallel-balancer.html>
> ([i915#4525])
> *
>
> igt@gem_exec_capture@pi@rcs0:
>
> o shard-iclb: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11332/shard-iclb6/igt@gem_exec_capture@p...@rcs0.html>
> -> INCOMPLETE
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-iclb5/igt@gem_exec_capture@p...@rcs0.html>
> ([i915#3371])
> *
>
> igt@gem_exec_fair@basic-deadline:
>
> o shard-skl: NOTRUN -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22498/shard-skl1/igt@gem_exec_f...@basic-deadline.html>
> ([i915#2846])
> *
>
> ig
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/4] drm/i915/ttm: make eviction mappable aware
That looks like a new issue. Filed the issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/5196
igt@syncobj_timeline@wait-all-for-submit-snapshot - fail - Failed assertion:
__syncobj_timeline_wait_ioctl(wait->fd, >wait) == 0, error: -62 != 0
Thanks,
Lakshmi.
-Original Message-
From: Auld, Matthew
Sent: Tuesday, March 1, 2022 12:39 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [CI,1/4]
drm/i915/ttm: make eviction mappable aware
On 01/03/2022 03:55, Patchwork wrote:
> *Patch Details*
> *Series:* series starting with [CI,1/4] drm/i915/ttm: make eviction
> mappable aware
> *URL:*https://patchwork.freedesktop.org/series/100818/
> <https://patchwork.freedesktop.org/series/100818/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11299_full -> Patchwork_22433_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_22433_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22433_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 -> 13)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22433_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@syncobj_timeline@wait-all-for-submit-snapshot:
> o shard-skl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11299/shard-skl1/igt@syncobj_timel...@wait-all-for-submit-snapshot.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-skl4/i
> gt@syncobj_timel...@wait-all-for-submit-snapshot.html>
Unrelated to this series.
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> *
>
>
> {igt@kms_plane_scaling@downscale-with-pixel-format-factor-0-25@pipe-a-edp-1-downscale-with-pixel-format}:
>
> o shard-iclb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-iclb8/igt@kms_plane_scaling@downscale-with-pixel-format-factor-0...@pipe-a-edp-1-downscale-with-pixel-format.html>
> +2 similar issues
> *
>
>
> {igt@kms_plane_scaling@downscale-with-rotation-factor-0-75@pipe-b-edp-1-downscale-with-rotation}:
>
> o {shard-rkl}: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-rkl-6/igt@kms_plane_scaling@downscale-with-rotation-factor-0...@pipe-b-edp-1-downscale-with-rotation.html>
> +8 similar issues
> *
>
>
> {igt@kms_plane_scaling@scaler-with-rotation-unity-scaling@pipe-d-hdmi-a-3-scaler-with-rotation}:
>
> o {shard-dg1}: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-dg1-18/igt@kms_plane_scaling@scaler-with-rotation-unity-scal...@pipe-d-hdmi-a-3-scaler-with-rotation.html>
> +3 similar issues
Fairly sure these are also unrelated to this series.
>
>
> New tests
>
> New tests have been introduced between CI_DRM_11299_full and
> Patchwork_22433_full:
>
>
> New IGT tests (1)
>
> *
> igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75@pipe-d-edp-1-planes-upscale-downscale:
> o Statuses : 1 pass(s)
> o Exec time: [1.28] s
>
>
> Known issues
>
> Here are the changes found in Patchwork_22433_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_ctx_param@set-priority-not-supported:
>
> o shard-iclb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-iclb8/igt@gem_ctx_pa...@set-priority-not-supported.html>
> ([fdo#109314])
> *
>
> igt@gem_eio@in-flight-contexts-10ms:
>
> o shard-iclb: NOTRUN -> TIMEOUT
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22433/shard-iclb8/igt@gem_...@in-flight-contexts-10ms.html>
> ([i915#3070])
> *
>
> igt@gem_exec_balancer@parallel-out-fence:
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Move power well code to a separate file (rev2)
Created https://gitlab.freedesktop.org/drm/intel/-/issues/5187 and re-reported
the issue.
igt@i915_selftest@mock@requests - incomplete - engine_unpark:\d+
GEM_BUG_ON(ce->timeline->seqno != .*)
Lakshmi.
-Original Message-
From: Deak, Imre
Sent: Friday, February 25, 2022 11:22 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Move power well code to a
separate file (rev2)
On Thu, Feb 24, 2022 at 12:01:18PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Move power well code to a separate file (rev2)
> URL : https://patchwork.freedesktop.org/series/100591/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11276_full -> Patchwork_22373_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22373_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22373_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (12 -> 12)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22373_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@mock@requests:
> - shard-skl: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-skl2/igt@i915_selftest@m...@requests.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-skl4/ig
> t@i915_selftest@m...@requests.html
This looks like
https://gitlab.freedesktop.org/drm/intel/-/issues/5183
which was only filed after this IGT result.
I can't see anything obvious in the logs, the same power wells get
enabled/disabled in both, this is the expected result as the patchset shouldn't
have any functional change.
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> *
> {igt@kms_plane_scaling@downscale-with-rotation-factor-2@pipe-d-downscale-with-rotation}:
> - {shard-dg1}:NOTRUN -> [INCOMPLETE][3]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-dg1-13/
> igt@kms_plane_scaling@downscale-with-rotation-factor-2@pipe-d-downscal
> e-with-rotation.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22373_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_create@create-massive:
> - shard-kbl: NOTRUN -> [DMESG-WARN][4] ([i915#4991])
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-kbl3/ig
> t@gem_cre...@create-massive.html
>
> * igt@gem_ctx_isolation@preservation-s3@vcs0:
> - shard-kbl: [PASS][5] -> [DMESG-WARN][6] ([i915#180]) +5
> similar issues
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-kbl7/igt@gem_ctx_isolation@preservation...@vcs0.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-kbl6/ig
> t@gem_ctx_isolation@preservation...@vcs0.html
>
> * igt@gem_eio@unwedge-stress:
> - shard-tglb: [PASS][7] -> [FAIL][8] ([i915#232])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-tglb7/igt@gem_...@unwedge-stress.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-tglb5/i
> gt@gem_...@unwedge-stress.html
>
> * igt@gem_exec_capture@pi@vecs0:
> - shard-skl: NOTRUN -> [INCOMPLETE][9] ([i915#4547])
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-skl7/ig
> t@gem_exec_capture@p...@vecs0.html
>
> * igt@gem_exec_fair@basic-none@rcs0:
> - shard-kbl: [PASS][10] -> [FAIL][11] ([i915#2842]) +1 similar
> issue
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-kbl1/igt@gem_exec_fair@basic-n...@rcs0.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-kbl4/ig
> t@gem_exec_fair@basic-n...@rcs0.html
>
> * igt@gem_exec_fair@basic-none@vcs1:
> - shard-iclb: NOTRUN -> [FAIL][12] ([i915#2842]) +4 similar issues
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22373/shard-iclb4/i
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dmc: Do not try loading wrong DMC version
Re-reported after addressing all the failures. See below for bug id's.
-Original Message-
From: De Marchi, Lucas
Sent: Friday, February 25, 2022 8:05 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/dmc: Do not try loading wrong
DMC version
On Fri, Feb 25, 2022 at 08:47:05AM +, Patchwork wrote:
>== Series Details ==
>
>Series: drm/i915/dmc: Do not try loading wrong DMC version
>URL : https://patchwork.freedesktop.org/series/100664/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_11279_full -> Patchwork_22393_full
>
>
>Summary
>---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22393_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22393_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
>
>
>Participating hosts (11 -> 11)
>--
>
> No changes in participating hosts
>
>Possible new issues
>---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22393_full:
>
>### IGT changes ###
>
> Possible regressions
>
> * igt@gem_eio@in-flight-suspend:
>- shard-skl: [PASS][1] -> [INCOMPLETE][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-skl8/igt@gem_...@in-flight-suspend.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-skl6/ig
> t@gem_...@in-flight-suspend.html
>
Lakshmi: This is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/4843
igt@gem_eio@in-flight-suspend - incomplete - PM: suspend entry (deep)
> * igt@kms_flip@busy-flip@a-hdmi-a1:
>- shard-glk: [PASS][3] -> [FAIL][4]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-glk1/igt@kms_flip@busy-f...@a-hdmi-a1.html
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-glk8/ig
> t@kms_flip@busy-f...@a-hdmi-a1.html
this could only be a regression if it was in another display_ver == 12.
Those are not.
Lakshmi: This is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/4628
igt@kms_flip@busy-flip@.* - fail - Failed assertion: do_page_flip(o, new_fb_id,
0) == -16,error: 0 != -16
>
>
> Warnings
>
> * igt@i915_pm_dc@dc3co-vpb-simulation:
>- shard-skl: [SKIP][5] ([fdo#109271] / [i915#658]) ->
> [INCOMPLETE][6]
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-skl10/igt@i915_pm...@dc3co-vpb-simulation.html
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-skl6/ig
> t@i915_pm...@dc3co-vpb-simulation.html
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
>- {shard-tglu}: NOTRUN -> [DMESG-WARN][7] +1 similar issue
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-tglu-1/
> igt@kms_plane@plane-panning-bottom-right-susp...@pipe-b-planes.html
this one woruld be suspicious, but the DMC issue there is caused by an earlier
error. Checking another run for this same machine, both are loading the same
DMC:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-tglu-1/boot9.txt
<7>[6.100322] i915 :00:02.0: [drm:intel_dmc_ucode_init [i915]] Loading
i915/tgl_dmc_ver2_12.bin
<7>[6.101182] i915 :00:02.0: [drm:intel_fbc_init [i915]] Sanitized
enable_fbc value: 1
<7>[6.102264] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM0 latency 3 (3.0 usec)
<7>[6.102480] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM1 latency 54 (54.0 usec)
<7>[6.102592] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM2 latency 54 (54.0 usec)
<7>[6.102712] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM3 latency 54 (54.0 usec)
<7>[6.102820] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM4 latency 54 (54.0 usec)
<7>[6.102977] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM5 latency 73 (73.0 usec)
<7>[6.103040] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM6 latency 110 (110.0 usec)
<7>[6.103176] i915 :00:02.0: [drm:intel_print_wm_latency [i915]] Gen9
Plane WM7 latency 115 (115.0 usec)
<6>[6.104018] i915 :00:02.0:
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg1: Update DMC_DEBUG3 register
Updated the filters.
-Original Message-
From: Roper, Matthew D
Sent: Monday, February 14, 2022 9:16 PM
To: intel-gfx@lists.freedesktop.org
Cc: Liu, Chuansheng ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg1: Update
DMC_DEBUG3 register
On Thu, Feb 10, 2022 at 07:10:32AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dg1: Update DMC_DEBUG3 register
> URL : https://patchwork.freedesktop.org/series/99942/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_22233_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22233_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22233_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (11 -> 12)
> --
>
> Additional (1): shard-rkl
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22233_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_pm_rpm@system-suspend-execbuf:
> - shard-iclb: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11207/shard-iclb2/igt@i915_pm_...@system-suspend-execbuf.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-iclb7/i
> gt@i915_pm_...@system-suspend-execbuf.html
Seems like a crash in the filesystem code, unrelated to the graphics driver.
Might be related to
https://gitlab.freedesktop.org/drm/intel/-/issues/5096 which is also a crash in
the filesystem code (although with a different signature).
[Lakshmi]
https://gitlab.freedesktop.org/drm/intel/-/issues/5164
igt@i915_pm_rpm@system-suspend-execbuf - incomplete - Workqueue:
ext4-rsv-conversion ext4_end_io_rsv_work
>
> * igt@kms_cursor_legacy@cursor-vs-flip-toggle:
> - shard-iclb: [PASS][3] -> [FAIL][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11207/shard-iclb6/igt@kms_cursor_leg...@cursor-vs-flip-toggle.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-iclb7/i
> gt@kms_cursor_leg...@cursor-vs-flip-toggle.html
Appears to be https://gitlab.freedesktop.org/drm/intel/-/issues/2370
[Lakshmi]
Issue looks similar to https://gitlab.freedesktop.org/drm/intel/-/issues/5072
>
> * igt@kms_flip@flip-vs-fences-interruptible@a-vga1:
> - shard-snb: [PASS][5] -> [INCOMPLETE][6]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11207/shard-snb5/igt@kms_flip@flip-vs-fences-interrupti...@a-vga1.html
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-snb4/ig
> t@kms_flip@flip-vs-fences-interrupti...@a-vga1.html
Appears to be https://gitlab.freedesktop.org/drm/intel/-/issues/5000
[Lakshmi] Updated#5000 filter.
None of these failures are caused by this series. Merging v2 (which is just a
commit message tweak) to drm-intel-next. CI for v2 failed because a KBL system
failed to boot, but that's not caused by this series. Thanks for the patch.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@syncobj_timeline@invalid-transfer-non-existent-point:
> - {shard-rkl}:NOTRUN -> [DMESG-WARN][7]
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-rkl-2/i
> gt@syncobj_timel...@invalid-transfer-non-existent-point.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22233_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@feature_discovery@psr2:
> - shard-iclb: NOTRUN -> [SKIP][8] ([i915#658])
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-iclb8/i
> gt@feature_discov...@psr2.html
>
> * igt@gem_exec_balancer@parallel-contexts:
> - shard-iclb: NOTRUN -> [SKIP][9] ([i915#4525]) +1 similar issue
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22233/shard-iclb8/i
> gt@gem_exec_balan...@parallel-contexts.html
>
> * igt@gem_exec_capture@pi@rcs0:
> - shard-skl: [PASS][10] -> [INCOMPLETE][11] ([i915#4547])
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11207/shard-skl2
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v2,1/2] drm/i915: Define MCH registers relative to MCHBAR_MIRROR_BASE
Below issue #3451 is closed, so created a new issue
https://gitlab.freedesktop.org/drm/intel/-/issues/5160
igt@kms_draw_crc@.* - fail - Failed assertion: !mismatch || igt_skip_crc_compare
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Wednesday, February 16, 2022 12:56 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [v2,1/2] drm/i915:
Define MCH registers relative to MCHBAR_MIRROR_BASE
On Wed, Feb 16, 2022 at 11:22:45AM +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v2,1/2] drm/i915: Define MCH registers relative
> to MCHBAR_MIRROR_BASE
> URL : https://patchwork.freedesktop.org/series/100153/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11230_full -> Patchwork_22278_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22278_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22278_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_22278_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
> - shard-glk: [PASS][1] -> [FAIL][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-glk3/igt@kms_draw_...@draw-method-rgb565-mmap-gtt-xtiled.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-glk6/ig
> t@kms_draw_...@draw-method-rgb565-mmap-gtt-xtiled.html
Seems to be https://gitlab.freedesktop.org/drm/intel/-/issues/3451 still
happening; not caused by the register definitions in this series.
Patches applied to drm-intel-next. Thanks Ville for the review.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@drm_import_export@import-close-race-prime:
> - {shard-rkl}:[PASS][3] -> [INCOMPLETE][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-rkl-2/igt@drm_import_exp...@import-close-race-prime.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-rkl-5/i
> gt@drm_import_exp...@import-close-race-prime.html
>
> * igt@gem_caching@read-writes:
> - {shard-rkl}:NOTRUN -> [FAIL][5]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-rkl-5/i
> gt@gem_cach...@read-writes.html
>
> * igt@gem_mmap_offset@open-flood:
> - {shard-rkl}:NOTRUN -> [INCOMPLETE][6] +2 similar issues
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-rkl-5/i
> gt@gem_mmap_off...@open-flood.html
>
> * igt@i915_selftest@live@gt_timelines:
> - {shard-rkl}:[PASS][7] -> ([PASS][8], [INCOMPLETE][9])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-rkl-1/igt@i915_selftest@live@gt_timelines.html
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-rkl-4/igt@i915_selftest@live@gt_timelines.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22278/shard-rkl-5/i
> gt@i915_selftest@live@gt_timelines.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22278_full that come from known
> issues:
>
> ### CI changes ###
>
> Possible fixes
>
> * boot:
> - {shard-rkl}:([PASS][10], [PASS][11], [PASS][12], [FAIL][13],
> [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19],
> [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25]) ->
> ([PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31],
> [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37],
> [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43],
> [PASS][44], [PASS][45])
>[10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-rkl-6/boot.html
>[11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-rkl-6/boot.html
>[12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11230/shard-rkl-6/boot.html
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: add Wa_14014947963 (rev2)
-Original Message-
From: Roper, Matthew D
Sent: Thursday, February 17, 2022 4:05 PM
To: intel-gfx@lists.freedesktop.org
Cc: Taylor, Clinton A ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: add
Wa_14014947963 (rev2)
On Fri, Feb 11, 2022 at 06:57:43AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dg2: add Wa_14014947963 (rev2)
> URL : https://patchwork.freedesktop.org/series/9/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11215_full -> Patchwork_22252_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22252_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22252_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (11 -> 12)
> --
>
> Additional (1): shard-rkl
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_22252_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_ctx_persistence@many-contexts:
> - shard-iclb: [PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11215/shard-iclb5/igt@gem_ctx_persiste...@many-contexts.html
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-iclb7/i
> gt@gem_ctx_persiste...@many-contexts.html
<4> [101.282625] WARNING: CPU: 5 PID: 175 at
drivers/gpu/drm/i915/gt/intel_execlists_submission.c:1908
process_csb+0x6d2/0x740 [i915]
which is GEM_WARN_ON(!*execlists->pending). It looks like we used to have
https://gitlab.freedesktop.org/drm/intel/-/issues/3057 for that warning. I
also see several other fdo bugs where the warning is sporadically tripped by
other tests. So it doesn't appear to be caused by this patch.
[Lakshmi] I have created https://gitlab.freedesktop.org/drm/intel/-/issues/5163
.
igt@gem_ctx_persistence@many-contexts - incomplete - WARNING: .* at
drivers/gpu/drm/i915/gt/intel_execlists_submission.c:\d+ process_csb,
Workqueue: events __intel_wakeref_put_work [i915]
Although the warning looks similar to #5153, call trace appears to be
different, so a new issue is created.
>
> * igt@kms_flip@flip-vs-suspend@b-vga1:
> - shard-snb: [PASS][3] -> [DMESG-WARN][4]
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11215/shard-snb4/igt@kms_flip@flip-vs-susp...@b-vga1.html
>[4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-snb6/ig
> t@kms_flip@flip-vs-susp...@b-vga1.html
<4> [58.614078] unchecked MSR access error: RDMSR from 0x1b0 at rIP:
0x8103a69f (intel_epb_restore+0xf/0xa0)
This isn't coming from the graphics driver. It's also seen on some of our
other suspend/resume tests. E.g.,
https://gitlab.freedesktop.org/drm/intel/-/issues/5090
Not caused by this test.
[Lakshmi] Yes, updated the filter.
Matt
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_whisper@basic-contexts-priority-all:
> - {shard-rkl}:NOTRUN -> [FAIL][5]
>[5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-rkl-5/i
> gt@gem_exec_whis...@basic-contexts-priority-all.html
>
> * igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-blt:
> - {shard-rkl}:NOTRUN -> [INCOMPLETE][6]
>[6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-rkl-5/i
> gt@kms_frontbuffer_track...@psr-1p-primscrn-spr-indfb-draw-blt.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_22252_full that come from known
> issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@feature_discovery@chamelium:
> - shard-iclb: NOTRUN -> [SKIP][7] ([fdo#111827])
>[7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-iclb5/i
> gt@feature_discov...@chamelium.html
>
> * igt@gem_ctx_isolation@preservation-s3@vcs0:
> - shard-kbl: [PASS][8] -> [DMESG-WARN][9] ([i915#180]) +1
> similar issue
>[8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11215/shard-kbl6/igt@gem_ctx_isolation@preservation...@vcs0.html
>[9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22252/shard-kbl1/i
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Refactor ADS access to use iosys_map (rev4)
Filed two new issues https://gitlab.freedesktop.org/drm/intel/-/issues/5162 igt@gem_exec_balancer@bonded-dual - incomplete - No logs https://gitlab.freedesktop.org/drm/intel/-/issues/5161 igt@gem_mmap_gtt@fault-concurrent-x - incomplete - unhandled error in i915_error_to_vmf_fault: -105 #5161 looks like a new issue but yet to happen on post-merge. Thanks, Lakshmi. -Original Message- From: De Marchi, Lucas Sent: Saturday, February 19, 2022 10:46 AM To: intel-gfx@lists.freedesktop.org Cc: Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/guc: Refactor ADS access to use iosys_map (rev4) On Sat, Feb 19, 2022 at 12:47:31PM +, Patchwork wrote: >== Series Details == > >Series: drm/i915/guc: Refactor ADS access to use iosys_map (rev4) >URL : https://patchwork.freedesktop.org/series/99711/ >State : failure > >== Summary == > >CI Bug Log - changes from CI_DRM_11250_full -> Patchwork_22334_full > > >Summary >--- > > **FAILURE** > > Serious unknown changes coming with Patchwork_22334_full absolutely > need to be verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_22334_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 -> 13) >-- > > No changes in participating hosts > >Possible new issues >--- > > Here are the unknown changes that may have been introduced in > Patchwork_22334_full: > >### IGT changes ### > > Possible regressions > > * igt@gem_exec_balancer@bonded-dual: >- shard-tglb: [PASS][1] -> [INCOMPLETE][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11250/shard-tglb6/igt@gem_exec_balan...@bonded-dual.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22334/shard-tglb6/i > gt@gem_exec_balan...@bonded-dual.html <7>[7.738070] i915 :00:02.0: [drm:intel_uc_init_early [i915]] enable_guc=0 (guc:no submission:no huc:no slpc:no) > > * igt@gem_mmap_gtt@fault-concurrent-x: >- shard-snb: [PASS][3] -> [INCOMPLETE][4] > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11250/shard-snb4/igt@gem_mmap_...@fault-concurrent-x.html > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22334/shard-snb6/ig > t@gem_mmap_...@fault-concurrent-x.html <7>[4.614922] i915 :00:02.0: [drm:intel_uc_init_early [i915]] enable_guc=0 (guc:no submission:no huc:no slpc:no) anything in this series can only change the behavior when using guc, so these failures can't be related to this series. Lucas De Marchi
Re: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: don't call free_mmap_offset when purging
I believe that's because of missing machine Missing (7): bat-dg1-6 bat-dg1-5 fi-bsw-cyan bat-adlp-6 bat-rpls-1 fi-bdw-samus bat-jsl-1 Looks like DG1 results were not used while the report is generated. Good that you checked the full logs. +@Latvala, Petri Lakshmi. -Original Message- From: Auld, Matthew Sent: Thursday, January 6, 2022 10:07 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: don't call free_mmap_offset when purging Lakshmi, any idea why this reports as success? Clicking on the "See full logs" for BAT there is a clear new failure on DG1 in one of the selftests, which is caused by this series. It also doesn't appear in the issues hit below. On 06/01/2022 12:32, Patchwork wrote: > *Patch Details* > *Series:* series starting with [v2,1/4] drm/i915: don't call > free_mmap_offset when purging > *URL:*https://patchwork.freedesktop.org/series/98548/ > <https://patchwork.freedesktop.org/series/98548/> > *State:* success > *Details:* > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html> > > > CI Bug Log - changes from CI_DRM_11052 -> Patchwork_21930 > > > Summary > > *SUCCESS* > > No regressions found. > > External URL: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/index.html > > > Participating hosts (44 -> 37) > > Missing (7): bat-dg1-6 bat-dg1-5 fi-bsw-cyan bat-adlp-6 bat-rpls-1 > fi-bdw-samus bat-jsl-1 > > > Known issues > > Here are the changes found in Patchwork_21930 that come from known issues: > > > IGT changes > > > Issues hit > > * > > igt@amdgpu/amd_basic@semaphore: > > o fi-bdw-5557u: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-bdw-5557u/igt@amdgpu/amd_ba...@semaphore.html> > (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +31 > similar issues > * > > igt@amdgpu/amd_cs_nop@sync-compute0: > > o fi-kbl-soraka: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-kbl-soraka/igt@amdgpu/amd_cs_...@sync-compute0.html> > (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +6 > similar issues > * > > igt@amdgpu/amd_prime@i915-to-amd: > > o fi-snb-2520m: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-snb-2520m/igt@amdgpu/amd_pr...@i915-to-amd.html> > (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +17 > similar issues > * > > igt@gem_exec_suspend@basic-s3: > > o fi-skl-6600u: NOTRUN -> INCOMPLETE > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-skl-6600u/igt@gem_exec_susp...@basic-s3.html> > (i915#4547 <https://gitlab.freedesktop.org/drm/intel/issues/4547>) > * > > igt@kms_chamelium@dp-crc-fast: > > o fi-bdw-5557u: NOTRUN -> SKIP > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-bdw-5557u/igt@kms_chamel...@dp-crc-fast.html> > (fdo#109271 > <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / > fdo#111827 > <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 > similar issues > > > Possible fixes > > * > > igt@gem_exec_suspend@basic-s3@smem: > > o fi-icl-u2: FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11052/fi-icl-u2/igt@gem_exec_suspend@basic...@smem.html> > (i915#1888 > <https://gitlab.freedesktop.org/drm/intel/issues/1888>) -> PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-icl-u2/igt@gem_exec_suspend@basic...@smem.html> > * > > igt@i915_selftest@live@gt_contexts: > > o fi-snb-2520m: DMESG-FAIL > > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11052/fi-snb-2520m/igt@i915_selftest@live@gt_contexts.html> > (i915#4610 > <https://gitlab.freedesktop.org/drm/intel/issues/4610>) -> PASS > > <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21930/fi-snb-2520m > /igt@i915_selftest@live@gt_contexts.html> > > > Build changes > > * Linux: CI_DRM_11052 -> Patchwork_21930 > > CI-20190529: 20190529 > CI_DRM_11052: 5926026a36a658f
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for More preparation for multi gt patches
Regressions are related to
https://gitlab.freedesktop.org/drm/intel/-/issues/2842
igt@gem_exec_fair@.* - fail - Failed assertion: iqr[nchild / 2] < result[nchild
/ 2], Child frame IQR .*ms exceeded median threshold .*m s
https://gitlab.freedesktop.org/drm/intel/-/issues/4817
igt@i915_suspend@sysfs-reader - incomplete - PM: suspend entry (deep)
I think re-reporting is not required as we may haver results from another rev.
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Friday, December 17, 2021 10:11 PM
To: intel-gfx@lists.freedesktop.org
Cc: Andi Shyti ; Vudum, Lakshminarayana
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for More preparation for multi gt
patches
On Wed, Dec 15, 2021 at 07:25:17AM +, Patchwork wrote:
> == Series Details ==
>
> Series: More preparation for multi gt patches
> URL : https://patchwork.freedesktop.org/series/98032/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11002_full -> Patchwork_21849_full
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_21849_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_21849_full, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (10 -> 10)
> --
>
> No changes in participating hosts
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_21849_full:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@gem_exec_fair@basic-none@vcs1:
> - shard-iclb: NOTRUN -> [FAIL][1]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21849/shard-iclb4/i
> gt@gem_exec_fair@basic-n...@vcs1.html
https://gitlab.freedesktop.org/drm/intel/-/issues/2842
>
> * igt@i915_suspend@sysfs-reader:
> - shard-skl: [PASS][2] -> [INCOMPLETE][3]
>[2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11002/shard-skl8/igt@i915_susp...@sysfs-reader.html
>[3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21849/shard-skl10/i
> gt@i915_susp...@sysfs-reader.html
Looks similar to this ADL-P issue that was seen only once:
https://gitlab.freedesktop.org/drm/intel/-/issues/4092
The first 10 patches have gone through several clean CI cycles now, so I've
pushed those to drm-intel-gt-next. There are just a couple minor comments on
the ggtt patches, so we can push the rest of those once the comments are
addressed.
BTW, there's one i915->gt reference in the display code that has moved from
display/intel_display.c to display/skl_universal_plane.c on drm-intel-next, but
that movement hasn't made its way to drm-intel-gt-next yet. This led to a
merge conflict while rebuilding drm-tip. I had to use a 'dim cat-to-fixup' to
apply the following diff to the drm-intel-gt-next merge commit:
diff --git a/drivers/gpu/drm/i915/display/skl_universal_plane.c
b/drivers/gpu/drm/i915/display/skl_universal_plane.c
index 158d89b8d490..b3162f49f341 100644
--- a/drivers/gpu/drm/i915/display/skl_universal_plane.c
+++ b/drivers/gpu/drm/i915/display/skl_universal_plane.c
@@ -1737,7 +1737,7 @@ static bool bo_has_valid_encryption(struct
drm_i915_gem_object *obj)
{
struct drm_i915_private *i915 = to_i915(obj->base.dev);
- return intel_pxp_key_check(>gt.pxp, obj, false) == 0;
+ return intel_pxp_key_check(_gt(i915)->pxp, obj, false) == 0;
}
static bool pxp_is_borked(struct drm_i915_gem_object *obj)
Matt
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_21849_full that come from known
> issues:
>
> ### CI changes ###
>
> Issues hit
>
> * boot:
> - shard-snb: ([PASS][4], [PASS][5], [PASS][6], [PASS][7],
> [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13],
> [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19],
> [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25],
> [PASS][26], [PASS][27], [PASS][28]) -> ([PASS][29], [PASS][30], [PASS][31],
> [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37],
> [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [FAIL][43],
> [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49],
> [PASS][50], [PASS][51], [PASS][52], [PASS][53]) ([i915#4338])
>[4]:
> https://intel-gfx-ci.01.
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/debugfs: add noreclaim annotations (rev2)
All are known issues. Re-reported the results.
-Original Message-
From: Auld, Matthew
Sent: Tuesday, December 14, 2021 1:26 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/debugfs: add noreclaim
annotations (rev2)
On 14/12/2021 04:55, Patchwork wrote:
> *Patch Details*
> *Series:* drm/i915/debugfs: add noreclaim annotations (rev2)
> *URL:*https://patchwork.freedesktop.org/series/97966/
> <https://patchwork.freedesktop.org/series/97966/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/index.html>
>
>
> CI Bug Log - changes from CI_DRM_10996_full -> Patchwork_21842_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_21842_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_21842_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false
> positives in CI.
>
>
> Participating hosts (10 -> 10)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_21842_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
>
> o
>
> shard-iclb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-iclb8/
> igt@kms_psr2...@overlay-primary-update-sf-dmg-area.html>
>
> o
>
> shard-tglb: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-tglb3/
> igt@kms_psr2...@overlay-primary-update-sf-dmg-area.html>
>
> *
>
> igt@perf@enable-disable:
>
> o shard-glk: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10996/shard-glk1/igt@p...@enable-disable.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-glk1/i
> gt@p...@enable-disable.html>
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area:
> o {shard-rkl}: NOTRUN -> SKIP
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-rkl-1/
> igt@kms_psr2...@primary-plane-update-sf-dmg-area.html>
>
These all look to be unrelated.
>
> Known issues
>
> Here are the changes found in Patchwork_21842_full that come from
> known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_ctx_isolation@preservation-s3@rcs0:
>
> o shard-apl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10996/shard-apl4/igt@gem_ctx_isolation@preservation...@rcs0.html>
> -> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-apl2/igt@gem_ctx_isolation@preservation...@rcs0.html>
> ([i915#180]) +2 similar issues
> *
>
> igt@gem_ctx_isolation@preservation-s3@vcs0:
>
> o shard-kbl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10996/shard-kbl6/igt@gem_ctx_isolation@preservation...@vcs0.html>
> -> DMESG-WARN
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-kbl7/igt@gem_ctx_isolation@preservation...@vcs0.html>
> ([i915#180]) +5 similar issues
> *
>
> igt@gem_exec_fair@basic-deadline:
>
> o shard-kbl: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10996/shard-kbl7/igt@gem_exec_f...@basic-deadline.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-kbl1/igt@gem_exec_f...@basic-deadline.html>
> ([i915#2846])
> *
>
> igt@gem_exec_fair@basic-none-share@rcs0:
>
> o shard-glk: PASS
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10996/shard-glk8/igt@gem_exec_fair@basic-none-sh...@rcs0.html>
> -> FAIL
>
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21842/shard-glk3/igt@gem_exec_fair@basic-none-sh...@rcs0.html>
> ([i915#2842])
> *
>
> igt@gem_exec_fair@basic-none-solo@rcs0:
>
>
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Don't leak the capture list items (rev2)
Regressions are related to https://gitlab.freedesktop.org/drm/intel/-/issues/4729 igt@kms_plane_cursor@.*<mailto:igt@kms_plane_cursor@.*> - fail - Failed assertion: !mismatch || igt_skip_crc_compare https://gitlab.freedesktop.org/drm/intel/-/issues/3653 igt@kms_big_fb.*<mailto:igt@kms_big_fb.*> - fail - Failed assertion: !mismatch || igt_skip_crc_compare Patch is re-reported. Thanks, Lakshmi. From: Thomas Hellström Sent: Monday, December 13, 2021 1:51 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Don't leak the capture list items (rev2) On Sat, 2021-12-11 at 09:49 +, Patchwork wrote: Patch Details Series: drm/i915: Don't leak the capture list items (rev2) URL: https://patchwork.freedesktop.org/series/97804/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21820/index.html CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21820_full Summary FAILURE Serious unknown changes coming with Patchwork_21820_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21820_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (10 -> 10) No changes in participating hosts Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21820_full: IGT changes Possible regressions * igt@kms_big_fb@linear-64bpp-rotate-180: * shard-iclb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-iclb2/igt@kms_big...@linear-64bpp-rotate-180.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21820/shard-iclb6/igt@kms_big...@linear-64bpp-rotate-180.html> * igt@kms_plane_cursor@pipe-a-viewport-size-64: * shard-glk: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-glk1/igt@kms_plane_cur...@pipe-a-viewport-size-64.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21820/shard-glk3/igt@kms_plane_cur...@pipe-a-viewport-size-64.html> Lakshmi, The above errors are unrelated. Thanks, Thomas
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: fix large buffer population trucation
Similar failures are noticed from https://patchwork.freedesktop.org/series/97804/ I address the failures and updated the filters. These are related to https://gitlab.freedesktop.org/drm/intel/-/issues/4729 igt@kms_plane_cursor@.*<mailto:igt@kms_plane_cursor@.*> - fail - Failed assertion: !mismatch || igt_skip_crc_compare https://gitlab.freedesktop.org/drm/intel/-/issues/3653 igt@kms_big_fb.*<mailto:igt@kms_big_fb.*> - fail - Failed assertion: !mismatch || igt_skip_crc_compare Thanks, Lakshmi. From: Matthew Auld Sent: Monday, December 13, 2021 5:09 AM To: Intel Graphics Development ; Vudum, Lakshminarayana Cc: Robert Beckett Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: fix large buffer population trucation On Sat, 11 Dec 2021 at 18:46, Patchwork mailto:patchw...@emeril.freedesktop.org>> wrote: Patch Details Series: drm/i915/ttm: fix large buffer population trucation URL: https://patchwork.freedesktop.org/series/97881/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21826/index.html CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21826_full Summary FAILURE Serious unknown changes coming with Patchwork_21826_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21826_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (10 -> 10) No changes in participating hosts Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21826_full: IGT changes Possible regressions * igt@kms_big_fb@linear-64bpp-rotate-180: * shard-iclb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-iclb2/igt@kms_big...@linear-64bpp-rotate-180.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21826/shard-iclb5/igt@kms_big...@linear-64bpp-rotate-180.html> * igt@kms_plane_cursor@pipe-a-viewport-size-64: * shard-glk: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-glk1/igt@kms_plane_cur...@pipe-a-viewport-size-64.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21826/shard-glk4/igt@kms_plane_cur...@pipe-a-viewport-size-64.html> Lakshmi, these are both false positives. Patch in question is specific to discrete platforms. * Known issues Here are the changes found in Patchwork_21826_full that come from known issues: CI changes Issues hit * boot: * shard-apl: (PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl2/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl2/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl2/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl3/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl3/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl3/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10988/shard-apl6/boot.html>) -> (PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21826/shard-apl8/boot.html>, PASS&l
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftest: Disable IRQ for timestamp calculation (rev3)
We have a bug https://gitlab.freedesktop.org/drm/intel/-/issues/4384 for the regression failure. Re-reported. Thanks, Lakshmi. -Original Message- From: Gupta, Anshuman Sent: Friday, December 3, 2021 12:40 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Cc: Dixit, Ashutosh ; Nilawar, Badal Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/selftest: Disable IRQ for timestamp calculation (rev3) On 2021-11-30 at 18:29:54 +, Patchwork wrote: > == Series Details == > > Series: drm/i915/selftest: Disable IRQ for timestamp calculation (rev3) > URL : https://patchwork.freedesktop.org/series/96853/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_10943_full -> Patchwork_21701_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_21701_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_21701_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (11 -> 11) > -- > > No changes in participating hosts > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_21701_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_fenced_exec_thrash@too-many-fences: > - shard-snb: [PASS][1] -> [INCOMPLETE][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10943/shard-snb4/igt@gem_fenced_exec_thr...@too-many-fences.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-snb5/ig > t@gem_fenced_exec_thr...@too-many-fences.html Above failure is unrelated to this patch. Pushed to drm-intel-next, thanks for review. Br, Anshuman. > > > Known issues > > > Here are the changes found in Patchwork_21701_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_exec_balancer@parallel-out-fence: > - shard-iclb: NOTRUN -> [SKIP][3] ([i915#4525]) >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-iclb6/i > gt@gem_exec_balan...@parallel-out-fence.html > > * igt@gem_exec_fair@basic-deadline: > - shard-glk: [PASS][4] -> [FAIL][5] ([i915#2846]) >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10943/shard-glk2/igt@gem_exec_f...@basic-deadline.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-glk5/ig > t@gem_exec_f...@basic-deadline.html > > * igt@gem_exec_fair@basic-none-rrul@rcs0: > - shard-kbl: [PASS][6] -> [FAIL][7] ([i915#2842]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10943/shard-kbl7/igt@gem_exec_fair@basic-none-r...@rcs0.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-kbl7/ig > t@gem_exec_fair@basic-none-r...@rcs0.html > > * igt@gem_exec_fair@basic-none@vcs1: > - shard-iclb: NOTRUN -> [FAIL][8] ([i915#2842]) >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-iclb4/i > gt@gem_exec_fair@basic-n...@vcs1.html > > * igt@gem_exec_fair@basic-pace-share@rcs0: > - shard-glk: [PASS][9] -> [FAIL][10] ([i915#2842]) +1 similar > issue >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10943/shard-glk9/igt@gem_exec_fair@basic-pace-sh...@rcs0.html >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-glk6/ig > t@gem_exec_fair@basic-pace-sh...@rcs0.html > > * igt@gem_lmem_swapping@heavy-verify-random: > - shard-kbl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-kbl3/ig > t@gem_lmem_swapp...@heavy-verify-random.html > > * igt@gem_userptr_blits@input-checking: > - shard-skl: NOTRUN -> [DMESG-WARN][12] ([i915#3002]) >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-skl4/ig > t@gem_userptr_bl...@input-checking.html > > * igt@gem_userptr_blits@vma-merge: > - shard-skl: NOTRUN -> [FAIL][13] ([i915#3318]) >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21701/shard-skl4/ig > t@gem_userptr_bl...@vma-merge.html > > * igt@i915_suspend@debugfs-reader: > - shard-kbl: [PASS][14] -> [DMESG-WARN][15] ([i915#180]) +4 > similar issue
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Update error capture code to avoid using the current vma state
Filed this issue and re-reported https://gitlab.freedesktop.org/drm/intel/-/issues/4664 igt@kms_flip@busy-flip@b-edp1 - incomplete - No warnings/errors Thanks, Lakshmi. From: Thomas Hellström Sent: Monday, November 29, 2021 9:46 PM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Update error capture code to avoid using the current vma state On Tue, 2021-11-30 at 01:50 +, Patchwork wrote: Patch Details Series: drm/i915: Update error capture code to avoid using the current vma state URL: https://patchwork.freedesktop.org/series/97385/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/index.html CI Bug Log - changes from CI_DRM_10939_full -> Patchwork_21696_full Summary FAILURE Serious unknown changes coming with Patchwork_21696_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21696_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (11 -> 10) Missing (1): pig-kbl-iris Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21696_full: IGT changes Possible regressions * igt@kms_flip@busy-flip@b-edp1: * shard-tglb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-tglb8/igt@kms_flip@busy-f...@b-edp1.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-tglb8/igt@kms_flip@busy-f...@b-edp1.html> Lakshmi, This failure is unrelated. Thanks, Thomas Known issues Here are the changes found in Patchwork_21696_full that come from known issues: CI changes Possible fixes * boot: * shard-skl: (PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl9/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl9/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl5/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl5/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl5/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl4/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl3/boot.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl3/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl1/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl10/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl10/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10939/shard-skl10/boot.html>) ([i915#4337]) -> (PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl9/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl9/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl9/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl8/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl7/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl6/boot.html>, PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21696/shard-skl6/boot.html>, PASS<https://intel-gfx-ci.01.org/t
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix DPT suspend/resume on !HAS_DISPLAY platforms
KBL issue is associated to https://gitlab.freedesktop.org/drm/intel/-/issues/4547 But not sure the component of the issue. Re-reported. Lakshmi. -Original Message- From: Deak, Imre Sent: Friday, November 26, 2021 5:59 AM To: Sarvela, Tomi P Cc: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana ; Latvala, Petri Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Fix DPT suspend/resume on !HAS_DISPLAY platforms On Fri, Nov 26, 2021 at 03:06:15PM +0200, Sarvela, Tomi P wrote: > The trace is full of ext4, so I'm siding on -rc2 issue. I can see lots of instances of the same stacktrace on fi-skl-6600u and one instance on shard-tglb7 at least since -rc1 (we don't have logs from before), but none on any of the other machines, except for this test run on shard-kbl6. > You can try re-testing the series to see if same failure happens again. I don't see a point in retesting, since I'm confident that the change has no effect on KBL. Looks like there's already https://gitlab.freedesktop.org/drm/intel/-/issues/4428 from 5.15.0 on the same shard-tglb7 as the above -rc1 failure and https://gitlab.freedesktop.org/drm/intel/-/issues/4547 on the same fi-skl-6600u as above. Imo KBL should be also added to the latter ticket. > > Tomi > > > From: Deak, Imre > > > > Hi, > > > > On Thu, Nov 25, 2021 at 10:38:35PM +, Patchwork wrote: > > > == Series Details == > > > > > > Series: drm/i915: Fix DPT suspend/resume on !HAS_DISPLAY platforms > > > URL : https://patchwork.freedesktop.org/series/97291/ > > > State : failure > > > > > > == Summary == > > > > > > CI Bug Log - changes from CI_DRM_10928_full -> > > > Patchwork_21682_full > > > > > > > > > Summary > > > --- > > > > > > **FAILURE** > > > > > > Serious unknown changes coming with Patchwork_21682_full > > > absolutely > > need to be > > > verified manually. > > > > > > If you think the reported changes have nothing to do with the changes > > > introduced in Patchwork_21682_full, please notify your bug team > > > to allow > > them > > > to document this new failure mode, which will reduce false positives in > > > CI. > > > > > > > > > > > > Participating hosts (11 -> 11) > > > -- > > > > > > No changes in participating hosts > > > > > > Possible new issues > > > --- > > > > > > Here are the unknown changes that may have been introduced in > > Patchwork_21682_full: > > > > > > ### IGT changes ### > > > > > > Possible regressions > > > > > > * igt@kms_flip@flip-vs-suspend@b-dp1: > > > - shard-kbl: [PASS][1] -> [INCOMPLETE][2] > > >[1]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10928/shard- > > kbl4/igt@kms_flip@flip-vs-susp...@b-dp1.html > > >[2]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21682/shard- > > kbl6/igt@kms_flip@flip-vs-susp...@b-dp1.html > > > > This is (happy that we have pstore logs!): > > > > <3>[ 121.347224] INFO: task kworker/u8:17:1044 blocked for more > > than 30 seconds. > > <3>[ 121.347231] Tainted: GW > > 5.16.0-rc2-CI-Patchwork_21682+ #1 > > <3>[ 121.347236] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > > disables this message. > > <6>[ 121.347241] task:kworker/u8:17 state:D stack:13456 pid: 1044 ppid: > >2 > > flags:0x4000 > > <6>[ 121.347250] Workqueue: writeback wb_workfn (flush-259:0) <6>[ > > 121.346993] schedule+0x3f/0xc0 <6>[ 121.346998] > > __bio_queue_enter+0x3a4/0x450 <6>[ 121.347006] ? > > finish_wait+0x80/0x80 <6>[ 121.347018] > > blk_mq_submit_bio+0x171/0xa30 <6>[ 121.347025] ? > > mpage_release_unused_pages+0x27b/0x290 > > <6>[ 121.347036] ? do_writepages+0xd3/0x1a0 <6>[ 121.347043] > > submit_bio_noacct+0x254/0x2a0 <6>[ 121.347055] > > ext4_io_submit+0x44/0x50 <6>[ 121.347060] > > ext4_writepages+0x32c/0x1070 <6>[ 121.347070] ? > > __lock_acquire+0x5c0/0xb70 <6>[ 121.347099] > > do_writepages+0xd3/0x1a0 <6>[ 121.347103] ? > > filemap_fdatawrite_wbc+0x4b/0x80 <6>[ 121.347117] > > filemap_fdatawrite_wbc+0x56/0x80 <6>[ 121.347124] > > fi
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: Async migration (rev11)
Filed two new issues https://gitlab.freedesktop.org/drm/intel/-/issues/4632 igt@gem_exec_create@forked@smem - incomplete - No warnings/errors https://gitlab.freedesktop.org/drm/intel/-/issues/4633 igt@kms_atomic_interruptible@universal-setplane-cursor@dp-1-pipe-a - incomplete - No warnings/errors re-reported. Lakshmi. From: Thomas Hellström Sent: Wednesday, November 24, 2021 2:56 AM To: intel-gfx@lists.freedesktop.org; Thomas Hellström ; Vudum, Lakshminarayana Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: Async migration (rev11) On 11/24/21 10:42, Patchwork wrote: Patch Details Series: drm/i915/ttm: Async migration (rev11) URL: https://patchwork.freedesktop.org/series/96798/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/index.html CI Bug Log - changes from CI_DRM_10921_full -> Patchwork_21672_full Summary FAILURE Serious unknown changes coming with Patchwork_21672_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21672_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (11 -> 11) No changes in participating hosts Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21672_full: IGT changes Possible regressions * igt@gem_exec_capture@pi@rcs0: * shard-skl: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10921/shard-skl7/igt@gem_exec_capture@p...@rcs0.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-skl2/igt@gem_exec_capture@p...@rcs0.html> * igt@gem_exec_create@forked@smem: * shard-kbl: NOTRUN -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-kbl7/igt@gem_exec_create@for...@smem.html> * igt@kms_atomic_interruptible@universal-setplane-cursor@dp-1-pipe-a: * shard-kbl: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10921/shard-kbl1/igt@kms_atomic_interruptible@universal-setplane-cur...@dp-1-pipe-a.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-kbl7/igt@kms_atomic_interruptible@universal-setplane-cur...@dp-1-pipe-a.html> +2 similar issues Lakshmi, These failures are unrelated. The first one appears also elsewhere, The other two appears to be a general problem with shard-kbl. Lots of random hangs from that one. /Thomas
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: placate scripts/kernel-doc
This failure is related to https://gitlab.freedesktop.org/drm/intel/-/issues/4547 Few tests - fail - This test was killed due to a kernel taint, INFO: task kworker/.* blocked for more than 30 seconds. Re-reproted. Thanks, Lakshmi. From: Matthew Auld Sent: Tuesday, November 23, 2021 1:45 AM To: Intel Graphics Development ; Vudum, Lakshminarayana Cc: Randy Dunlap Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: placate scripts/kernel-doc On Tue, 23 Nov 2021 at 05:56, Patchwork mailto:patchw...@emeril.freedesktop.org>> wrote: Patch Details Series: drm/i915/gem: placate scripts/kernel-doc URL: https://patchwork.freedesktop.org/series/97190/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/index.html CI Bug Log - changes from CI_DRM_10917 -> Patchwork_21664 Summary FAILURE Serious unknown changes coming with Patchwork_21664 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21664, please notify your bug team 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_21664/index.html Participating hosts (40 -> 34) Additional (1): fi-kbl-soraka Missing (7): bat-dg1-6 fi-tgl-u2 fi-bsw-cyan bat-adlp-6 bat-adlp-4 bat-jsl-2 bat-jsl-1 Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21664: IGT changes Possible regressions * igt@gem_exec_suspend@basic-s3: * fi-skl-6600u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10917/fi-skl-6600u/igt@gem_exec_susp...@basic-s3.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-skl-6600u/igt@gem_exec_susp...@basic-s3.html> Lakshmi, another false positive it seems. The patch in question is only fixing kernel-doc. Pushed to drm-intel-gt-next. Thanks. * Known issues Here are the changes found in Patchwork_21664 that come from known issues: IGT changes Issues hit * igt@amdgpu/amd_basic@semaphore: * fi-bdw-5557u: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-bdw-5557u/igt@amdgpu/amd_ba...@semaphore.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +31 similar issues * igt@gem_exec_fence@basic-busy@bcs0: * fi-kbl-soraka: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-soraka/igt@gem_exec_fence@basic-b...@bcs0.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +2 similar issues * igt@gem_exec_suspend@basic-s0: * fi-kbl-soraka: NOTRUN -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-soraka/igt@gem_exec_susp...@basic-s0.html> (i915#4221<https://gitlab.freedesktop.org/drm/intel/issues/4221>) * igt@gem_huc_copy@huc-copy: * fi-kbl-8809g: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-8809g/igt@gem_huc_c...@huc-copy.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#2190<https://gitlab.freedesktop.org/drm/intel/issues/2190>) * igt@i915_selftest@live@hangcheck: * fi-snb-2600: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10917/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html> (i915#3921<https://gitlab.freedesktop.org/drm/intel/issues/3921>) * igt@kms_chamelium@dp-crc-fast: * fi-bdw-5557u: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-bdw-5557u/igt@kms_chamel...@dp-crc-fast.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 similar issues * igt@kms_chamelium@hdmi-edid-read: * fi-kbl-8809g: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-8809g/igt@kms_chamel...@hdmi-edid-read.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 similar issues * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d: * fi-kbl-8809g: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-8809g/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-d.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#533<https://gitlab.freedesktop.org/drm/intel/issues/533>) * igt@kms_psr@cursor_plane_move: * fi-kbl-8809g: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21664/fi-kbl-8809g/igt@kms_psr@cursor_plane_move.html> (fdo#109271<http
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: Fix error code in i915_ttm_eviction_valuable()
Filed https://gitlab.freedesktop.org/drm/intel/-/issues/4577 and re-reported. igt@kms_flip@dpms-vs-vblank-race-interruptible@b-dp1 - incomplete - No warnings/errors Thanks, Lakshmi. -Original Message- From: Matthew Auld Sent: Monday, November 22, 2021 6:32 AM To: Dan Carpenter ; Vudum, Lakshminarayana Cc: Intel Graphics Development Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: Fix error code in i915_ttm_eviction_valuable() On Mon, 22 Nov 2021 at 14:21, Dan Carpenter wrote: > > On Mon, Nov 22, 2021 at 02:08:39PM -, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915/ttm: Fix error code in i915_ttm_eviction_valuable() > > URL : https://patchwork.freedesktop.org/series/97151/ > > State : failure > > Who is supposed to be reading these? I feel like there should be a > human reading them but it's not me... The system is broken, but who > is fixing it? > > regards, > dan carpenter > > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_10911_full -> Patchwork_21650_full > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_21650_full absolutely need > > to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_21650_full, please notify your bug team to allow > > them > > to document this new failure mode, which will reduce false positives in > > CI. > > > > > > > > Participating hosts (11 -> 11) > > -- > > > > No changes in participating hosts > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > > Patchwork_21650_full: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@kms_flip@dpms-vs-vblank-race-interruptible@b-dp1: > > - shard-kbl: [PASS][1] -> [INCOMPLETE][2] > >[1]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-kbl2/igt@kms_flip@dpms-vs-vblank-race-interrupti...@b-dp1.html > >[2]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21650/shard-kbl7/ > > igt@kms_flip@dpms-vs-vblank-race-interrupti...@b-dp1.html Lakshmi, this one is for sure a false positive. Patch pushed to drm-intel-gt-next. Thanks. > > > > > > Known issues > > > > > > Here are the changes found in Patchwork_21650_full that come from known > > issues: > > > > ### CI changes ### > > > > Possible fixes > > > > * boot: > > - shard-glk: ([FAIL][3], [PASS][4], [PASS][5], [PASS][6], > > [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], > > [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], > > [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], > > [PASS][25], [PASS][26], [PASS][27]) ([i915#4392]) -> ([PASS][28], > > [PASS][29], [PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], > > [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], > > [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], > > [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52]) > >[3]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk3/boot.html > >[4]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk9/boot.html > >[5]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk9/boot.html > >[6]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk9/boot.html > >[7]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk8/boot.html > >[8]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk8/boot.html > >[9]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk8/boot.html > >[10]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk7/boot.html > >[11]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk7/boot.html > >[12]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk7/boot.html > >[13]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk6/boot.html > >[14]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10911/shard-glk6/
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/ttm: Async migration (rev7)
We have https://gitlab.freedesktop.org/drm/intel/-/issues/4547 for the regression on SKL. Few tests - fail - This test was killed due to a kernel taint, INFO: task kworker/.* blocked for more than 30 seconds. Thanks, Lakshmi. From: Thomas Hellström Sent: Monday, November 22, 2021 6:54 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/ttm: Async migration (rev7) On 11/22/21 15:02, Patchwork wrote: Patch Details Series: drm/i915/ttm: Async migration (rev7) URL: https://patchwork.freedesktop.org/series/96798/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21651/index.html CI Bug Log - changes from CI_DRM_10913 -> Patchwork_21651 Summary FAILURE Serious unknown changes coming with Patchwork_21651 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21651, please notify your bug team 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_21651/index.html Participating hosts (43 -> 34) Missing (9): bat-dg1-6 fi-tgl-u2 bat-dg1-5 fi-icl-u2 fi-bsw-cyan bat-adlp-6 bat-adlp-4 bat-jsl-2 bat-jsl-1 Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21651: IGT changes Possible regressions * igt@gem_exec_suspend@basic-s3: * fi-skl-6600u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10913/fi-skl-6600u/igt@gem_exec_susp...@basic-s3.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21651/fi-skl-6600u/igt@gem_exec_susp...@basic-s3.html> Lakshmi, This failure is unrelated, and occurs on the same machine with a more or less identical signature on CI_DRM_10901 Thanks, Thomas
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/rpm: Enable runtime pm autosuspend by default (rev4)
Re-reported. -Original Message- From: Gupta, Anshuman Sent: Friday, November 19, 2021 2:40 AM To: Vudum, Lakshminarayana Cc: Tangudu, Tilak ; intel-gfx@lists.freedesktop.org Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/rpm: Enable runtime pm autosuspend by default (rev4) Hi Lakshmi , Could you please create a gitlab issue for the below failure and re-report the results. Below failure is present on drm-tip builds as well not related to this patch. • igt@kms_psr@primary_page_flip: o fi-skl-6600u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10896/fi-skl-6600u/igt@kms_psr@primary_page_flip.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-skl-6600u/igt@kms_psr@primary_page_flip.html Thanks , Anshuman Gupta From: Intel-gfx On Behalf Of Patchwork Sent: Thursday, November 18, 2021 4:29 AM To: Tangudu, Tilak Cc: intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/rpm: Enable runtime pm autosuspend by default (rev4) Patch Details Series: drm/i915/rpm: Enable runtime pm autosuspend by default (rev4) URL: https://patchwork.freedesktop.org/series/96741/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/index.html CI Bug Log - changes from CI_DRM_10896 -> Patchwork_21622 Summary FAILURE Serious unknown changes coming with Patchwork_21622 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21622, please notify your bug team 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_21622/index.html Participating hosts (40 -> 34) Additional (1): fi-tgl-1115g4 Missing (7): bat-dg1-6 fi-tgl-u2 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 bat-jsl-2 bat-jsl-1 Possible new issues Here are the unknown changes that may have been introduced in Patchwork_21622: IGT changes Possible regressions • igt@gem_lmem_swapping@verify-random: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@gem_lmem_swapp...@verify-random.html +3 similar issues • igt@kms_psr@primary_page_flip: o fi-skl-6600u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10896/fi-skl-6600u/igt@kms_psr@primary_page_flip.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-skl-6600u/igt@kms_psr@primary_page_flip.html Known issues Here are the changes found in Patchwork_21622 that come from known issues: IGT changes Issues hit • igt@amdgpu/amd_basic@query-info: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@amdgpu/amd_ba...@query-info.html (https://bugs.freedesktop.org/show_bug.cgi?id=109315) • igt@amdgpu/amd_cs_nop@nop-gfx0: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@amdgpu/amd_cs_...@nop-gfx0.html (https://bugs.freedesktop.org/show_bug.cgi?id=109315 / https://gitlab.freedesktop.org/drm/intel/issues/2575) +16 similar issues • igt@amdgpu/amd_cs_nop@sync-fork-compute0: o fi-snb-2600: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-snb-2600/igt@amdgpu/amd_cs_...@sync-fork-compute0.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +17 similar issues • igt@gem_huc_copy@huc-copy: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@gem_huc_c...@huc-copy.html (https://gitlab.freedesktop.org/drm/intel/issues/2190) • igt@i915_pm_backlight@basic-brightness: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@i915_pm_backli...@basic-brightness.html (https://gitlab.freedesktop.org/drm/intel/issues/1155) • igt@i915_selftest@live@execlists: o fi-bsw-nick: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10896/fi-bsw-nick/igt@i915_selftest@l...@execlists.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-bsw-nick/igt@i915_selftest@l...@execlists.html (https://gitlab.freedesktop.org/drm/intel/issues/2940) • igt@i915_selftest@live@workarounds: o fi-rkl-guc: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10896/fi-rkl-guc/igt@i915_selftest@l...@workarounds.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-rkl-guc/igt@i915_selftest@l...@workarounds.html (https://gitlab.freedesktop.org/drm/intel/issues/4433) • igt@kms_chamelium@common-hpd-after-suspend: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@kms_chamel...@common-hpd-after-suspend.html (https://bugs.freedesktop.org/show_bug.cgi?id=111827) +8 similar issues • igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: o fi-tgl-1115g4: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21622/fi-tgl-1115g4/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic
