Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for drm/xe: Use ttm_uncached for BO with NEEDS_UC flag (rev2)
Date: Tue, 18 Jun 2024 13:42:32 +0200	[thread overview]
Message-ID: <5a7412e7-636b-425a-bbd7-4f48a86d8955@intel.com> (raw)
In-Reply-To: <171871054579.103379.9406133499403683961@a6498e030952>



On 18.06.2024 13:35, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe: Use ttm_uncached for BO with NEEDS_UC flag (rev2)
> URL   : https://patchwork.freedesktop.org/series/134580/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165_BAT -> xe-pw-134580v2_BAT
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-134580v2_BAT absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-134580v2_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 (5 -> 5)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-134580v2_BAT:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

unrelated

> 
>   * igt@kms_flip@basic-flip-vs-wf_vblank@b-dp3:
>     - bat-dg2-oem2:       [PASS][1] -> [ABORT][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@b-dp3.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-134580v2/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@b-dp3.html

Dynamic subtest B-DP3: SUCCESS (1.025s)

This test caused an abort condition: Lockdep not active

<7>[  309.551991] [IGT] kms_flip: starting dynamic subtest C-DP3
<7>[  309.553397] xe 0000:03:00.0: [drm:drm_mode_addfb2 [drm]] [FB:292]
<7>[  309.554465] xe 0000:03:00.0: [drm:drm_mode_addfb2 [drm]] [FB:293]
<4>[  309.561185] ------------[ cut here ]------------
<4>[  309.561189] DEBUG_LOCKS_WARN_ON(debug_atomic_read(nr_unused_locks)
!= nr_unused)
<4>[  309.561192] WARNING: CPU: 4 PID: 1149 at
kernel/locking/lockdep_proc.c:283 lockdep_stats_show+0xb99/0xe30


> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in xe-pw-134580v2_BAT that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@kms_flip@basic-flip-vs-wf_vblank:
>     - bat-dg2-oem2:       [PASS][3] -> [ABORT][4] ([Intel XE#1553])
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-134580v2/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank.html
> 
>   * igt@kms_flip@basic-flip-vs-wf_vblank@c-dp3:
>     - bat-dg2-oem2:       [PASS][5] -> [DMESG-WARN][6] ([Intel XE#1553])
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@c-dp3.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-134580v2/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@c-dp3.html
> 
>   
>   [Intel XE#1553]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1553
> 
> 
> Build changes
> -------------
> 
>   * Linux: xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165 -> xe-pw-134580v2
> 
>   IGT_7890: a137e386eba9f46f838315f5d93b87561691d45e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   xe-1489-b3cee15446d95e97d9d663cdcbc611e698354165: b3cee15446d95e97d9d663cdcbc611e698354165
>   xe-pw-134580v2: 134580v2
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-134580v2/index.html
> 

  reply	other threads:[~2024-06-18 11:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 10:49 [PATCH v2] drm/xe: Use ttm_uncached for BO with NEEDS_UC flag Michal Wajdeczko
2024-06-18 10:55 ` ✓ CI.Patch_applied: success for drm/xe: Use ttm_uncached for BO with NEEDS_UC flag (rev2) Patchwork
2024-06-18 10:55 ` ✓ CI.checkpatch: " Patchwork
2024-06-18 10:56 ` ✓ CI.KUnit: " Patchwork
2024-06-18 11:08 ` ✓ CI.Build: " Patchwork
2024-06-18 11:10 ` ✗ CI.Hooks: failure " Patchwork
2024-06-18 11:11 ` ✓ CI.checksparse: success " Patchwork
2024-06-18 11:35 ` ✗ CI.BAT: failure " Patchwork
2024-06-18 11:42   ` Michal Wajdeczko [this message]
2024-06-18 19:16 ` [PATCH v2] drm/xe: Use ttm_uncached for BO with NEEDS_UC flag Matt Roper
2024-06-18 22:46 ` ✗ CI.FULL: failure for drm/xe: Use ttm_uncached for BO with NEEDS_UC flag (rev2) Patchwork
2024-06-19 11:22   ` Michal Wajdeczko

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=5a7412e7-636b-425a-bbd7-4f48a86d8955@intel.com \
    --to=michal.wajdeczko@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox