From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: SAGV fixes (rev2)
Date: Fri, 18 Feb 2022 06:41:30 +0200 [thread overview]
Message-ID: <Yg8jehUkAODEmlxG@intel.com> (raw)
In-Reply-To: <164512822157.18053.8104488537367014984@emeril.freedesktop.org>
On Thu, Feb 17, 2022 at 08:03:41PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: SAGV fixes (rev2)
> URL : https://patchwork.freedesktop.org/series/100091/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11239_full -> Patchwork_22302_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22302_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22302_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_22302_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_cursor_legacy@all-pipes-forked-bo:
> - shard-iclb: [PASS][1] -> [INCOMPLETE][2] +10 similar issues
Argh. These are due to the extra debug spam from
intel_bw_atomic_check() since that now goes throug the full function
a lot more.
So either we just nuke a bunch of those debugs, or I guess we do it a
bit more like what Stan suggested and try to check more carefully if the
inputs to to the QGV calculation actually changed.
I guess I'll try the latter approach, in case those debugs are actually
useful. The challenge will be doing that and keeping the patch looking
reasonable for stable...
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2022-02-18 4:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:42 [Intel-gfx] [PATCH v2 0/6] drm/i915: SAGV fixes Ville Syrjala
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 1/6] drm/i915: Correctly populate use_sagv_wm for all pipes Ville Syrjala
2022-02-16 17:42 ` Ville Syrjala
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 2/6] drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV Ville Syrjala
2022-02-16 17:42 ` Ville Syrjala
2022-02-17 18:29 ` [Intel-gfx] " Lisovskiy, Stanislav
2022-02-17 18:29 ` Lisovskiy, Stanislav
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 3/6] drm/i915: Split pre-icl vs. icl+ SAGV hooks apart Ville Syrjala
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 4/6] drm/i915: Pimp icl+ sagv pre/post update Ville Syrjala
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 5/6] drm/i915: Extract icl_qgv_points_mask() Ville Syrjala
2022-02-16 17:42 ` [Intel-gfx] [PATCH v2 6/6] drm/i915: Extract intel_bw_check_data_rate() Ville Syrjala
2022-02-17 18:33 ` Lisovskiy, Stanislav
2022-02-17 11:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: SAGV fixes (rev2) Patchwork
2022-02-17 20:03 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-18 4:41 ` Ville Syrjälä [this message]
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=Yg8jehUkAODEmlxG@intel.com \
--to=ville.syrjala@linux.intel.com \
--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 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.