Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ i915.CI.BAT: failure for drm/i915: Some fixes and cleanups
Date: Wed, 25 Mar 2026 22:38:05 +0200	[thread overview]
Message-ID: <acRHrf97geJux96t@intel.com> (raw)
In-Reply-To: <177446096314.397746.15426606883297672242@a3b018990fe9>

On Wed, Mar 25, 2026 at 05:49:23PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Some fixes and cleanups
> URL   : https://patchwork.freedesktop.org/series/163857/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_18213 -> Patchwork_163857v1
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_163857v1 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_163857v1, 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_163857v1/index.html
> 
> Participating hosts (41 -> 39)
> ------------------------------
> 
>   Missing    (2): bat-dg2-13 fi-snb-2520m 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_163857v1:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_busy@basic@flip:
>     - fi-bsw-n3050:       [PASS][1] -> [DMESG-WARN][2] +1 other test dmesg-warn
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/fi-bsw-n3050/igt@kms_busy@basic@flip.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-bsw-n3050/igt@kms_busy@basic@flip.html

<3> [252.057088] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe C (start=16166 end=16167) time 403 us, min 1063, max 1079, scanline start 1052, end 1080

Unrelated to these changes.

> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in Patchwork_163857v1 that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@dmabuf@all-tests@dma_fence_chain:
>     - fi-glk-j4005:       NOTRUN -> [SKIP][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-glk-j4005/igt@dmabuf@all-tests@dma_fence_chain.html
> 
>   * igt@i915_selftest@live:
>     - bat-mtlp-8:         [PASS][4] -> [DMESG-FAIL][5] ([i915#12061]) +1 other test dmesg-fail
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/bat-mtlp-8/igt@i915_selftest@live.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/bat-mtlp-8/igt@i915_selftest@live.html
>     - bat-adlp-11:        [PASS][6] -> [DMESG-FAIL][7] ([i915#12964]) +1 other test dmesg-fail
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/bat-adlp-11/igt@i915_selftest@live.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/bat-adlp-11/igt@i915_selftest@live.html
> 
>   * igt@i915_selftest@live@workarounds:
>     - bat-arlh-3:         [PASS][8] -> [DMESG-FAIL][9] ([i915#12061]) +1 other test dmesg-fail
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/bat-arlh-3/igt@i915_selftest@live@workarounds.html
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/bat-arlh-3/igt@i915_selftest@live@workarounds.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@i915_selftest@live:
>     - fi-glk-j4005:       [ABORT][10] ([i915#15825]) -> [PASS][11]
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/fi-glk-j4005/igt@i915_selftest@live.html
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-glk-j4005/igt@i915_selftest@live.html
> 
>   * igt@i915_selftest@live@gt_mocs:
>     - fi-glk-j4005:       [ABORT][12] -> [PASS][13]
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/fi-glk-j4005/igt@i915_selftest@live@gt_mocs.html
>    [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-glk-j4005/igt@i915_selftest@live@gt_mocs.html
> 
>   * igt@i915_selftest@live@hugepages:
>     - fi-glk-j4005:       [DMESG-FAIL][14] -> [PASS][15]
>    [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/fi-glk-j4005/igt@i915_selftest@live@hugepages.html
>    [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-glk-j4005/igt@i915_selftest@live@hugepages.html
> 
>   * igt@kms_hdmi_inject@inject-audio:
>     - fi-tgl-1115g4:      [FAIL][16] ([i915#14867]) -> [PASS][17]
>    [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18213/fi-tgl-1115g4/igt@kms_hdmi_inject@inject-audio.html
>    [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/fi-tgl-1115g4/igt@kms_hdmi_inject@inject-audio.html
> 
>   
>   [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
>   [i915#12964]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12964
>   [i915#14867]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14867
>   [i915#15825]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15825
> 
> 
> Build changes
> -------------
> 
>   * Linux: CI_DRM_18213 -> Patchwork_163857v1
> 
>   CI-20190529: 20190529
>   CI_DRM_18213: cfe3d5f3eb5cf3b8aff1710c1c5c1d666f932aa8 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGT_8825: 531ebe0606453021b88f794aad255d9e1a234d3d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   Patchwork_163857v1: cfe3d5f3eb5cf3b8aff1710c1c5c1d666f932aa8 @ git://anongit.freedesktop.org/gfx-ci/linux
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_163857v1/index.html

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2026-03-25 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 13:58 [PATCH 0/6] drm/i915: Some fixes and cleanups Ville Syrjala
2026-03-25 13:58 ` [PATCH 1/6] drm/i915/cdclk: Do the full CDCLK dance for min_voltage_level changes Ville Syrjala
2026-03-25 15:40   ` Michał Grzelak
2026-03-25 13:58 ` [PATCH 2/6] drm/i915/dp: Use crtc_state->enhanced_framing properly on ivb/hsw CPU eDP Ville Syrjala
2026-03-25 15:44   ` Michał Grzelak
2026-03-25 13:58 ` [PATCH 3/6] drm/i915: Split the pipe_src dump to its own line Ville Syrjala
2026-03-25 15:44   ` Michał Grzelak
2026-03-25 13:58 ` [PATCH 4/6] drm/i915: Include the crtc min_voltage_level in the state dump Ville Syrjala
2026-03-25 15:45   ` Michał Grzelak
2026-03-25 13:58 ` [PATCH 5/6] drm/i915: Eliminate out of place "HBlank" CamelCase Ville Syrjala
2026-03-25 15:46   ` Michał Grzelak
2026-03-25 13:58 ` [PATCH 6/6] drm/i915: Move the sharness filter dump next to pfit Ville Syrjala
2026-03-25 15:46   ` Michał Grzelak
2026-03-25 21:15     ` Michał Grzelak
2026-03-25 17:49 ` ✗ i915.CI.BAT: failure for drm/i915: Some fixes and cleanups Patchwork
2026-03-25 20:38   ` Ville Syrjälä [this message]
2026-03-27 14:13 ` ✗ i915.CI.BAT: failure for drm/i915: Some fixes and cleanups (rev2) Patchwork
2026-03-27 21:14 ` ✓ i915.CI.BAT: success for drm/i915: Some fixes and cleanups (rev3) Patchwork
2026-03-29  0:50 ` ✗ i915.CI.Full: failure " 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=acRHrf97geJux96t@intel.com \
    --to=ville.syrjala@linux.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