From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: SSEU handling updates (rev2)
Date: Mon, 23 May 2022 16:31:52 -0700 [thread overview]
Message-ID: <YowZaLiRYIWEMWcl@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <165334101320.9281.12824970684177033061@emeril.freedesktop.org>
On Mon, May 23, 2022 at 09:23:33PM +0000, 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-5557u/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_gttfill@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_copy@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@live@hangcheck.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/bat-dg1-6/igt@i915_selftest@live@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@live@hangcheck.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-snb-2600/igt@i915_selftest@live@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@basic@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_chamelium@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_legacy@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]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/bat-adlp-4/igt@kms_flip@basic-flip-vs-modeset@b-edp1.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/bat-adlp-4/igt@kms_flip@basic-flip-vs-modeset@b-edp1.html
>
> * igt@kms_force_connector_basic@force-load-detect:
> - fi-tgl-u2: NOTRUN -> [SKIP][14] ([fdo#109285])
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/igt@kms_force_connector_basic@force-load-detect.html
>
> * igt@kms_setmode@basic-clone-single-crtc:
> - fi-tgl-u2: NOTRUN -> [SKIP][15] ([i915#3555])
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/igt@kms_setmode@basic-clone-single-crtc.html
>
> * igt@prime_vgem@basic-userptr:
> - fi-tgl-u2: NOTRUN -> [SKIP][16] ([i915#3301])
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-tgl-u2/igt@prime_vgem@basic-userptr.html
>
> * igt@runner@aborted:
> - fi-icl-u2: NOTRUN -> [FAIL][17] ([i915#4312])
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-icl-u2/igt@runner@aborted.html
>
>
> #### Possible fixes ####
>
> * igt@gem_exec_suspend@basic-s0@smem:
> - {fi-ehl-2}: [DMESG-WARN][18] ([i915#5122]) -> [PASS][19]
> [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/fi-ehl-2/igt@gem_exec_suspend@basic-s0@smem.html
> [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/fi-ehl-2/igt@gem_exec_suspend@basic-s0@smem.html
>
> * igt@kms_flip@basic-plain-flip@a-edp1:
> - bat-adlp-4: [DMESG-WARN][20] ([i915#3576]) -> [PASS][21] +2 similar issues
> [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11693/bat-adlp-4/igt@kms_flip@basic-plain-flip@a-edp1.html
> [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/bat-adlp-4/igt@kms_flip@basic-plain-flip@a-edp1.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
> [fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
> [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
> [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
> [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
> [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
> [i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
> [i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
> [i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
> [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
> [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
> [i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
> [i915#4890]: https://gitlab.freedesktop.org/drm/intel/issues/4890
> [i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
> [i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_11693 -> Patchwork_104244v2
>
> CI-20190529: 20190529
> CI_DRM_11693: 14289bc81309b2126f4ba9f339837dacf34ddf9c @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_6485: 51663917b40d36086cc1c555ce4f67b22937694d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_104244v2: 14289bc81309b2126f4ba9f339837dacf34ddf9c @ git://anongit.freedesktop.org/gfx-ci/linux
>
>
> ### Linux commits
>
> e3100146e9db drm/i915/pvc: Add SSEU changes
> 920dde2397e4 drm/i915/sseu: Disassociate internal subslice mask representation from uapi
> 67224fa58023 drm/i915/sseu: Don't try to store EU mask internally in UAPI format
> ec3d320f5b49 drm/i915/sseu: Simplify gen11+ SSEU handling
> f00314dcab14 drm/i915/xehp: Drop GETPARAM lookups of I915_PARAM_[SUB]SLICE_MASK
> 5edcd0a4da5f drm/i915/xehp: Use separate sseu init function
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104244v2/index.html
--
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2022-05-23 23:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 23:04 [Intel-gfx] [PATCH v4 0/6] i915: SSEU handling updates Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 1/6] drm/i915/xehp: Use separate sseu init function Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 2/6] drm/i915/xehp: Drop GETPARAM lookups of I915_PARAM_[SUB]SLICE_MASK Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 3/6] drm/i915/sseu: Simplify gen11+ SSEU handling Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 4/6] drm/i915/sseu: Don't try to store EU mask internally in UAPI format Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 5/6] drm/i915/sseu: Disassociate internal subslice mask representation from uapi Matt Roper
2022-05-23 7:59 ` Tvrtko Ursulin
2022-05-23 20:45 ` [Intel-gfx] [PATCH v5 " Matt Roper
2022-06-01 8:18 ` Balasubramani Vivekanandan
2022-06-01 14:40 ` Matt Roper
2022-05-20 23:04 ` [Intel-gfx] [PATCH v4 6/6] drm/i915/pvc: Add SSEU changes Matt Roper
2022-05-20 23:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: SSEU handling updates Patchwork
2022-05-20 23:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-20 23:55 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-05-23 21:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: SSEU handling updates (rev2) Patchwork
2022-05-23 21:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-23 21:23 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-05-23 23:31 ` Matt Roper [this message]
2022-05-24 16:20 ` Vudum, Lakshminarayana
2022-05-24 2:51 ` Patchwork
2022-05-24 5:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-24 7:07 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-24 7:32 ` [Intel-gfx] [PATCH v4 0/6] i915: SSEU handling updates Tvrtko Ursulin
2022-05-24 16:12 ` [Intel-gfx] ✓ Fi.CI.IGT: success for i915: SSEU handling updates (rev2) Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YowZaLiRYIWEMWcl@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox