From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Support run ticks for multi-queue use case (rev5)
Date: Fri, 8 May 2026 13:30:55 -0700 [thread overview]
Message-ID: <af5H/xUDNxXML8+s@soc-5CG1426VCC.clients.intel.com> (raw)
In-Reply-To: <177820923342.50384.9295520146602172162@5ab824fced77>
On Fri, May 08, 2026 at 03:00:33AM +0000, Patchwork wrote:
> Patch Details
>
> Series: Support run ticks for multi-queue use case (rev5)
> URL: https://patchwork.freedesktop.org/series/164654/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164654v5/index.html
>
>CI Bug Log - changes from xe-5014-7b68adb8e6366263ebebbc100fc0828a163e4005_FULL
> -> xe-pw-164654v5_FULL
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-164654v5_FULL absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-164654v5_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 (2 -> 2)
>
> No changes in participating hosts
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> xe-pw-164654v5_FULL:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_fbcon_fbt@psr-suspend:
>
> * shard-lnl: PASS -> FAIL
Failure is similar to this instance, so not something new but fails
randomly even without this series
https://intel-gfx-ci.01.org/tree/intel-xe/xe-5018-36eddf6e5c9411ad95c4939b092ed1ea77f13d61/shard-lnl-4/igt@kms_fbcon_fbt@psr-suspend.html
> * igt@xe_exec_reset@long-spin-comp-reuse-many-preempt-threads:
>
> * shard-bmg: PASS -> FAIL
This test ran fine on v4 series of this patch, so it's not related to
this series. Also below tests exercise the TDR path and pass locally on
my setup:
xe_exec_reset@cancel-timeslice-preempt (takes 10 seconds to pass)
xe_exec_reset@cancel-timeslice-many-preempt (takes 20 seconds to pass)
> * igt@xe_exec_system_allocator@process-many-large-execqueues-new:
>
> * shard-bmg: NOTRUN -> ABORT
> * shard-lnl: PASS -> ABORT
This one is failing in other instances of CI runs as well, so not
related to this series
Umesh
>
>Known issues
>
prev parent reply other threads:[~2026-05-08 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 16:20 [PATCH v5 00/11] Support run ticks for multi-queue use case Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 01/11] drm/xe/lrc: Use 64 bit ctx timestamp in the LRC snapshot Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 02/11] drm/xe: Add timestamp_ms to " Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 03/11] drm/xe/lrc: Refactor xe_lrc_timestamp to simplify logic Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 04/11] drm/xe/multi_queue: Refactor check for multi queue support for engine class Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 05/11] drm/xe/multi_queue: Store primary LRC and position info in LRC Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 06/11] drm/xe/multi_queue: Add helpers to access CS QUEUE TIMESTAMP from lrc Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 07/11] drm/xe/lrc: Refactor out engine id to hwe conversion Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 08/11] drm/xe/multi_queue: Capture queue run times for active queues Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 09/11] drm/xe/multi_queue: Add trace event for the multi queue timestamp Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 10/11] drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for multi-queue Umesh Nerlige Ramappa
2026-05-07 16:29 ` Umesh Nerlige Ramappa
2026-05-07 16:20 ` [PATCH v5 11/11] drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register Umesh Nerlige Ramappa
2026-05-07 16:31 ` ✗ CI.checkpatch: warning for Support run ticks for multi-queue use case (rev5) Patchwork
2026-05-07 16:32 ` ✓ CI.KUnit: success " Patchwork
2026-05-07 17:41 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-08 3:00 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-08 20:30 ` Umesh Nerlige Ramappa [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=af5H/xUDNxXML8+s@soc-5CG1426VCC.clients.intel.com \
--to=umesh.nerlige.ramappa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).