From: Imre Deak <imre.deak@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.BAT: failure for drm/i915/dp: Work around a DSC pixel throughput issue (rev3)
Date: Mon, 22 Sep 2025 19:04:31 +0300 [thread overview]
Message-ID: <aNFzjwViWnPHjOMk@ideak-desk> (raw)
In-Reply-To: <175855614562.354824.565057761427346128@1538d3639d33>
On Mon, Sep 22, 2025 at 03:49:05PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dp: Work around a DSC pixel throughput issue (rev3)
> URL : https://patchwork.freedesktop.org/series/154737/
> State : failure
Hi CI team,
could you please re-report this result?
The issue is unrelated, it's present in base-line IGT/xe testruns as
well and has now an open ticket too:
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6201
I suppose the cibug filter could be simply set to all platforms for this
issue.
Thanks,
Imre
>
> == Summary ==
>
> CI Bug Log - changes from xe-3812-c4d19320a0e2f7d8dec97d4a59309349a3a63ec0_BAT -> xe-pw-154737v3_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-154737v3_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-154737v3_BAT, 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.
>
>
>
> Participating hosts (11 -> 9)
> ------------------------------
>
> Missing (2): bat-adlp-vm bat-ptl-vm
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-154737v3_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_force_connector_basic@force-edid:
> - bat-bmg-2: NOTRUN -> [ABORT][1]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154737v3/bat-bmg-2/igt@kms_force_connector_basic@force-edid.html
>
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_force_connector_basic@force-connector-state:
> - {bat-ptl-1}: [ABORT][2] ([Intel XE#6201]) -> [ABORT][3]
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-3812-c4d19320a0e2f7d8dec97d4a59309349a3a63ec0/bat-ptl-1/igt@kms_force_connector_basic@force-connector-state.html
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154737v3/bat-ptl-1/igt@kms_force_connector_basic@force-connector-state.html
>
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-154737v3_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Possible fixes ####
>
> * igt@kms_force_connector_basic@force-connector-state:
> - bat-bmg-2: [ABORT][4] ([Intel XE#6201]) -> [PASS][5]
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-3812-c4d19320a0e2f7d8dec97d4a59309349a3a63ec0/bat-bmg-2/igt@kms_force_connector_basic@force-connector-state.html
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154737v3/bat-bmg-2/igt@kms_force_connector_basic@force-connector-state.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [Intel XE#6201]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6201
>
>
> Build changes
> -------------
>
> * IGT: IGT_8546 -> IGT_8547
> * Linux: xe-3812-c4d19320a0e2f7d8dec97d4a59309349a3a63ec0 -> xe-pw-154737v3
>
> IGT_8546: 8546
> IGT_8547: 8547
> xe-3812-c4d19320a0e2f7d8dec97d4a59309349a3a63ec0: c4d19320a0e2f7d8dec97d4a59309349a3a63ec0
> xe-pw-154737v3: 154737v3
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154737v3/index.html
next prev parent reply other threads:[~2025-09-22 16:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 21:12 [PATCH 0/5] drm/i915/dp: Work around a DSC pixel throughput issue Imre Deak
2025-09-18 21:12 ` [PATCH 1/5] drm/dp: Add quirk for Synaptics DSC throughput link-bpp limit Imre Deak
2025-09-20 17:18 ` kernel test robot
2025-09-22 13:46 ` [PATCH v2 " Imre Deak
2025-09-18 21:12 ` [PATCH 2/5] drm/i915/dp: Calculate DSC slice count based on per-slice peak throughput Imre Deak
2025-09-22 19:34 ` Ville Syrjälä
2025-09-23 11:47 ` Imre Deak
2025-09-18 21:12 ` [PATCH 3/5] drm/i915/dp: Pass DPCD device descriptor to intel_dp_get_dsc_sink_cap() Imre Deak
2025-09-18 21:12 ` [PATCH 4/5] drm/i915/dp: Verify branch devices' overall pixel throughput/line width Imre Deak
2025-09-22 19:35 ` Ville Syrjälä
2025-09-22 20:06 ` Ville Syrjälä
2025-09-23 12:00 ` Imre Deak
2025-09-18 21:12 ` [PATCH 5/5] drm/i915/dp: Handle Synaptics DSC throughput link-bpp quirk Imre Deak
2025-09-22 13:46 ` [PATCH v2 " Imre Deak
2025-09-22 20:17 ` Ville Syrjälä
2025-09-23 12:08 ` Imre Deak
2025-09-25 22:08 ` [PATCH v4 " Imre Deak
2025-09-18 21:57 ` ✗ CI.checkpatch: warning for drm/i915/dp: Work around a DSC pixel throughput issue Patchwork
2025-09-18 21:58 ` ✓ CI.KUnit: success " Patchwork
2025-09-18 22:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 23:32 ` ✓ i915.CI.BAT: " Patchwork
2025-09-19 21:10 ` ✓ i915.CI.Full: " Patchwork
2025-09-22 14:32 ` ✓ i915.CI.BAT: success for drm/i915/dp: Work around a DSC pixel throughput issue (rev3) Patchwork
2025-09-22 14:35 ` ✗ CI.checkpatch: warning " Patchwork
2025-09-22 14:36 ` ✓ CI.KUnit: success " Patchwork
2025-09-22 15:49 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-09-22 16:04 ` Imre Deak [this message]
2025-09-24 5:44 ` Ravali, JupallyX
2025-09-22 16:19 ` ✗ i915.CI.Full: " Patchwork
2025-09-22 19:03 ` ✓ Xe.CI.Full: success " 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=aNFzjwViWnPHjOMk@ideak-desk \
--to=imre.deak@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=intel-xe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.