public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for lib/debugfs: Sanity check even discarded CRCs (rev3)
Date: Fri, 15 May 2020 21:52:20 +0300	[thread overview]
Message-ID: <20200515185220.GN6112@intel.com> (raw)
In-Reply-To: <158956647040.26211.8314577379076963373@emeril.freedesktop.org>

On Fri, May 15, 2020 at 06:14:30PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: lib/debugfs: Sanity check even discarded CRCs (rev3)
> URL   : https://patchwork.freedesktop.org/series/53982/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_8488_full -> IGTPW_4574_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_4574_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_4574_full, 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/IGTPW_4574/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_4574_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_ctx_ringsize@idle@rcs0:
>     - shard-iclb:         [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8488/shard-iclb8/igt@gem_ctx_ringsize@idle@rcs0.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4574/shard-iclb5/igt@gem_ctx_ringsize@idle@rcs0.html
> 
>   * igt@kms_cursor_edge_walk@pipe-a-256x256-bottom-edge:
>     - shard-iclb:         [PASS][3] -> [WARN][4] +33 similar issues
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8488/shard-iclb8/igt@kms_cursor_edge_walk@pipe-a-256x256-bottom-edge.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4574/shard-iclb8/igt@kms_cursor_edge_walk@pipe-a-256x256-bottom-edge.html

Somewhat surprising result. kms_cursor_edge_walk sees zeroed
crcs all the time, but no other test ever sees them. Wasn't
quite expecting that.

Hmm. Now that I think about it IIRC there was some problem
with CRCs when all planes are turned off. I think the spec
even says the dmux crc source shouldn't be used with all planes
turned off, but I seem to recall the problem only manifesting
for a single frame when transitioning between no-planes vs. some
planes.

However I don't think kms_cursor_edge_walk should even be turning
off all the planes. This would seem to need a deeper investigation.

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2020-05-15 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 10:57 [igt-dev] [PATCH i-g-t] lib/debugfs: Sanity check even discarded CRCs Ville Syrjala
2018-12-13 11:19 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2018-12-13 20:51 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
2018-12-19 14:46 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib/debugfs: Sanity check even discarded CRCs (rev2) Patchwork
2020-05-15 14:38 ` [igt-dev] [PATCH i-g-t v2] lib/debugfs: Sanity check even discarded CRCs Ville Syrjala
2020-05-18 19:06   ` Souza, Jose
2020-05-15 15:12 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/debugfs: Sanity check even discarded CRCs (rev3) Patchwork
2020-05-15 18:14 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-05-15 18:52   ` 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=20200515185220.GN6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@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