From: Jani Nikula <jani.nikula@intel.com>
To: I915-ci-infra@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: add dedicated lock for each sideband (rev3)
Date: Wed, 30 Oct 2024 14:59:14 +0200 [thread overview]
Message-ID: <87h68tlpb1.fsf@intel.com> (raw)
In-Reply-To: <875xpanebc.fsf@intel.com>
On Wed, 30 Oct 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 30 Oct 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
>> == Series Details ==
>>
>> Series: drm/i915: add dedicated lock for each sideband (rev3)
>> URL : https://patchwork.freedesktop.org/series/139437/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_15607 -> Patchwork_139437v3
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with Patchwork_139437v3 absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_139437v3, please notify your bug team (I915-ci-infra@lists.freedesktop.org) 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_139437v3/index.html
>>
>> Participating hosts (47 -> 46)
>> ------------------------------
>>
>> Missing (1): fi-snb-2520m
>>
>> Possible new issues
>> -------------------
>>
>> Here are the unknown changes that may have been introduced in Patchwork_139437v3:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * igt@i915_selftest@live:
>> - bat-jsl-1: [PASS][1] -> [DMESG-WARN][2] +1 other test dmesg-warn
>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15607/bat-jsl-1/igt@i915_selftest@live.html
>> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_139437v3/bat-jsl-1/igt@i915_selftest@live.html
>
> Unrelated.
And by that I mean, please re-report.
>
>>
>>
>> Known issues
>> ------------
>>
>> Here are the changes found in Patchwork_139437v3 that come from known issues:
>>
>> ### IGT changes ###
>>
>> #### Possible fixes ####
>>
>> * igt@i915_selftest@live:
>> - bat-mtlp-8: [ABORT][3] ([i915#12133] / [i915#12216]) -> [PASS][4]
>> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15607/bat-mtlp-8/igt@i915_selftest@live.html
>> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_139437v3/bat-mtlp-8/igt@i915_selftest@live.html
>>
>> * igt@i915_selftest@live@workarounds:
>> - bat-mtlp-8: [ABORT][5] ([i915#12216]) -> [PASS][6]
>> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15607/bat-mtlp-8/igt@i915_selftest@live@workarounds.html
>> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_139437v3/bat-mtlp-8/igt@i915_selftest@live@workarounds.html
>>
>> * igt@kms_chamelium_frames@dp-crc-fast:
>> - bat-dg2-13: [DMESG-WARN][7] ([i915#12253]) -> [PASS][8]
>> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15607/bat-dg2-13/igt@kms_chamelium_frames@dp-crc-fast.html
>> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_139437v3/bat-dg2-13/igt@kms_chamelium_frames@dp-crc-fast.html
>>
>>
>> [i915#12133]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12133
>> [i915#12216]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12216
>> [i915#12253]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12253
>>
>>
>> Build changes
>> -------------
>>
>> * Linux: CI_DRM_15607 -> Patchwork_139437v3
>>
>> CI-20190529: 20190529
>> CI_DRM_15607: fb2691707e2d5a8c704ae5e48bc5a314a308b0e0 @ git://anongit.freedesktop.org/gfx-ci/linux
>> IGT_8087: 7abd9c49a49a9ff1f3300d7c51a92a5af8a789f1 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>> Patchwork_139437v3: fb2691707e2d5a8c704ae5e48bc5a314a308b0e0 @ git://anongit.freedesktop.org/gfx-ci/linux
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_139437v3/index.html
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-30 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 9:25 [RESEND 0/4] drm/i915: add dedicated lock for each sideband Jani Nikula
2024-10-29 9:25 ` [RESEND 1/4] drm/i915/sbi: add intel_sbi_{lock,unlock}() Jani Nikula
2024-10-29 9:25 ` [RESEND 2/4] drm/i915/sbi: add a dedicated mutex for LPT/WPT IOSF sideband Jani Nikula
2024-10-29 9:25 ` [RESEND 3/4] drm/i915: add a dedicated mutex for VLV/CHV " Jani Nikula
2024-10-29 9:25 ` [RESEND 4/4] drm/i915: hide VLV PUNIT IOSF sideband qos handling better Jani Nikula
2024-10-29 11:16 ` [RESEND 0/4] drm/i915: add dedicated lock for each sideband Hogander, Jouni
2024-11-05 11:05 ` Jani Nikula
2024-10-29 18:50 ` ✗ Fi.CI.SPARSE: warning for drm/i915: add dedicated lock for each sideband (rev2) Patchwork
2024-10-29 19:16 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-30 0:15 ` ✗ Fi.CI.SPARSE: warning for drm/i915: add dedicated lock for each sideband (rev3) Patchwork
2024-10-30 0:24 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-30 9:13 ` Jani Nikula
2024-10-30 12:59 ` Jani Nikula [this message]
2024-11-04 6:50 ` Illipilli, TejasreeX
2024-11-04 6:35 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-04 11:49 ` ✗ Fi.CI.SPARSE: warning for drm/i915: add dedicated lock for each sideband (rev4) Patchwork
2024-11-04 12:51 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-04 22:04 ` ✓ Fi.CI.IGT: " 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=87h68tlpb1.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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