Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe: Make PPHWSP size explicit in xe_gt_lrc_size()
Date: Mon, 31 Mar 2025 09:26:01 -0300	[thread overview]
Message-ID: <174342396193.1873.13338596709689658292@intel.com> (raw)
In-Reply-To: <174324046232.17810.2186731408193589187@e6b6f09ec485>

Quoting Patchwork (2025-03-29 06:27:42-03:00)
>== Series Details ==
>
>Series: drm/xe: Make PPHWSP size explicit in xe_gt_lrc_size()
>URL   : https://patchwork.freedesktop.org/series/146970/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from xe-2871-4cac9bb1b5db81d533be95f97dd30c03a8733871_FULL -> xe-pw-146970v1_FULL
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with xe-pw-146970v1_FULL absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in xe-pw-146970v1_FULL, 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 (4 -> 4)
>------------------------------
>
>  No changes in participating hosts
>
>Possible new issues
>-------------------
>
>  Here are the unknown changes that may have been introduced in xe-pw-146970v1_FULL:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@kms_pipe_stress@stress-xrgb8888-untiled:
>    - shard-bmg:          [PASS][1] -> [INCOMPLETE][2]
>   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2871-4cac9bb1b5db81d533be95f97dd30c03a8733871/shard-bmg-1/igt@kms_pipe_stress@stress-xrgb8888-untiled.html
>   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-bmg-2/igt@kms_pipe_stress@stress-xrgb8888-untiled.html

Looking at
https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-bmg-2/dmesg15.txt,
I can see the following line:

  <7>[  432.399076] [IGT] kms_pipe_stress: finished subtest stress-xrgb8888-untiled, SUCCESS

Meaning that this test finished successfully. So this is probably some
coordination issue between CI and the test runner?

>
>  * igt@kms_plane_lowres@tiling-4@pipe-d-hdmi-a-3:
>    - shard-bmg:          NOTRUN -> [INCOMPLETE][3] +1 other test incomplete
>   [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-bmg-8/igt@kms_plane_lowres@tiling-4@pipe-d-hdmi-a-3.html

Similarly, the log in
https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-bmg-8/dmesg19.txt
contains:

  <7>[  358.222106] [IGT] kms_plane_lowres: finished subtest pipe-A-HDMI-A-3, SUCCESS

>
>  * igt@kms_rotation_crc@multiplane-rotation-cropping-top:
>    - shard-dg2-set2:     [PASS][4] -> [INCOMPLETE][5]
>   [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2871-4cac9bb1b5db81d533be95f97dd30c03a8733871/shard-dg2-463/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html
>   [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-dg2-433/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html

For this one, the final line of
https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-dg2-433/dmesg16.txt
seems to be the same as for the log presented in
https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-dg2-433/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html.

That said, this should not be related to this patch, which is
non-functional and should be affecting other platforms as well if there
was an issue in the code update.

>
>  * igt@xe_compute_preempt@compute-preempt-many:
>    - shard-bmg:          [PASS][6] -> [FAIL][7] +1 other test fail
>   [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2871-4cac9bb1b5db81d533be95f97dd30c03a8733871/shard-bmg-1/igt@xe_compute_preempt@compute-preempt-many.html
>   [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146970v1/shard-bmg-8/igt@xe_compute_preempt@compute-preempt-many.html

This seems to be the same as
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4278.

--
Gustavo Sousa

  reply	other threads:[~2025-03-31 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 16:50 [PATCH] drm/xe: Make PPHWSP size explicit in xe_gt_lrc_size() Gustavo Sousa
2025-03-28 17:35 ` Matt Roper
2025-03-28 18:39 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-28 18:39 ` ✓ CI.checkpatch: " Patchwork
2025-03-28 18:41 ` ✓ CI.KUnit: " Patchwork
2025-03-28 18:57 ` ✓ CI.Build: " Patchwork
2025-03-28 19:00 ` ✓ CI.Hooks: " Patchwork
2025-03-28 19:01 ` ✓ CI.checksparse: " Patchwork
2025-03-28 19:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-29  9:27 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-31 12:26   ` Gustavo Sousa [this message]
2025-03-31 17:13 ` [PATCH] " Lucas De Marchi

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=174342396193.1873.13338596709689658292@intel.com \
    --to=gustavo.sousa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox