Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: "Lin, Shuicheng" <shuicheng.lin@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Misc fix for xe_guc_ct.c (rev2)
Date: Wed, 25 Feb 2026 09:28:40 -0800	[thread overview]
Message-ID: <20260225172840.GP4694@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <BL1PR11MB54477BA143E124F7C47C5752EA75A@BL1PR11MB5447.namprd11.prod.outlook.com>

On Wed, Feb 25, 2026 at 04:15:30PM +0000, Lin, Shuicheng wrote:
> >Possible regressions
> 
> >igt@xe_exec_fault_mode@twice-bindexecqueue-imm:
>     >shard-lnl: NOTRUN -> ABORT<https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161990v2/shard-lnl-7/igt@xe_exec_fault_mode@twice-bindexecqueue-imm.html> +23 other tests abort
> 
> >igt@xe_exec_system_allocator@threads-shared-vm-many-execqueues-mmap-prefetch:
>     >shard-bmg: NOTRUN -> ABORT<https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161990v2/shard-bmg-5/igt@xe_exec_system_allocator@threads-shared-vm-many-execqueues-mmap-prefetch.html> +23 other tests abort
> I checked the failure log, both test cases are passed, and there is “possible recursive locking detected”, which is not related to my code.
> So, the regression is not caused by my patch.

Applied to drm-xe-next.  Thanks for the patches and reviews.


Matt

> Thanks.
> 
> Best Regards
> Shuicheng

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

      reply	other threads:[~2026-02-25 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 16:23 [PATCH 0/2] Misc fix for xe_guc_ct.c Shuicheng Lin
2026-02-23 16:23 ` [PATCH 1/2] drm/xe/guc: Accumulate CT H2G retry sleep budget Shuicheng Lin
2026-02-23 16:59   ` Matthew Brost
2026-02-23 16:23 ` [PATCH 2/2] drm/xe/guc: Refine CT queue checks and log formatting Shuicheng Lin
2026-02-23 17:05   ` Matthew Brost
2026-02-23 16:35 ` ✓ CI.KUnit: success for Misc fix for xe_guc_ct.c Patchwork
2026-02-24 21:26 ` ✓ CI.KUnit: success for Misc fix for xe_guc_ct.c (rev2) Patchwork
2026-02-24 21:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-25  5:48 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-25 16:15   ` Lin, Shuicheng
2026-02-25 17:28     ` Matt Roper [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=20260225172840.GP4694@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=shuicheng.lin@intel.com \
    /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