public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.FULL: failure for *AuxCCS handling and render compression modifiers
Date: Tue, 24 Mar 2026 08:25:51 +0000	[thread overview]
Message-ID: <95dfe41d-e64b-418d-bacb-46d4b0afca7a@igalia.com> (raw)
In-Reply-To: <acG6g7YHbhcnszY9@intel.com>


On 23/03/2026 22:11, Rodrigo Vivi wrote:
> On Mon, Mar 23, 2026 at 09:42:30AM +0000, Tvrtko Ursulin wrote:
>>
>> On 21/03/2026 17:52, Patchwork wrote:
>>> *Patch Details*
>>> *Series:*	*AuxCCS handling and render compression modifiers
>>> *URL:*	https://patchwork.freedesktop.org/series/163610/ <https://
>>> patchwork.freedesktop.org/series/163610/>
>>> *State:*	failure
>>> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-163610v1/
>>> index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-163610v1/
>>> index.html>
>>>
>>>
>>>    CI Bug Log - changes from xe-4753-
>>>    f64c2a6453d0e0196f9697b8429bf97b1da1807e_FULL -> xe-pw-163610v1_FULL
>>>
>>>
>>>      Summary
>>>
>>> *FAILURE*
>>>
>>> Serious unknown changes coming with xe-pw-163610v1_FULL absolutely need
>>> to be
>>> verified manually.
>>>
>>> If you think the reported changes have nothing to do with the changes
>>> introduced in xe-pw-163610v1_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-163610v1_FULL:
>>>
>>>
>>>        IGT changes
>>>
>>>
>>>          Possible regressions
>>>
>>>    *
>>>
>>>      igt@kms_fbcon_fbt@fbc-suspend:
>>>
>>>        o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>>>          xe-4753-f64c2a6453d0e0196f9697b8429bf97b1da1807e/shard-lnl-3/
>>>          igt@kms_fbcon_fbt@fbc-suspend.html> -> INCOMPLETE <https://
>>>          intel-gfx-ci.01.org/tree/intel-xe/xe-pw-163610v1/shard-lnl-7/
>>>          igt@kms_fbcon_fbt@fbc-suspend.html>
>>
>> There is already an incomplete in the history at
>> xe-4754-f202c0d0dece0eeefb750a6a9d80f4b7442529f4 so I am pretty sure this
>> one is unrelated.
>>
>>>    *
>>>
>>>      igt@xe_eudebug@basic-vm-access-userptr:
>>>
>>>        o shard-bmg: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/
>>>          intel-xe/xe-pw-163610v1/shard-bmg-9/igt@xe_eudebug@basic-vm-
>>>          access-userptr.html> +6 other tests skip
>>
>> '/sys/class/drm/card0/device/enable_eudebug' sysfs attribute not found, EU
>> DEBUG not supported
>>
>> Which is the same as all the history for this test I can see so it is some
>> CI confusion that it is flagging this as new.
> 
> I agree, let's ignore those.
> But I couldn't merge it. It is conflicting when trying to apply on drm-xe-next
> or even on drm-tip.
> 
> Perhaps worth a rebase or am I missing something?

Right, trivial conflict due
61e7649a1a25 ("drm/xe/vf: Improve getting clean NULL context")
which landed yesterday.

I will repost shortly.

Regards,

Tvrtko

  reply	other threads:[~2026-03-24  8:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 17:02 [PATCH v24 00/12] *AuxCCS handling and render compression modifiers Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 01/12] drm/xe: Rename XE_BO_FLAG_SCANOUT to XE_BO_FLAG_FORCE_WC Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 02/12] drm/xe: Use write-combine mapping when populating DPT Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 03/12] drm/xe/xelpg: Limit AuxCCS ring buffer programming to Alderlake Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 04/12] drm/xe/xelp: Quiesce memory traffic before invalidating AuxCCS Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 05/12] drm/xe/xelp: Wait for AuxCCS invalidation to complete Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 06/12] drm/xe: Move aux table invalidation to ring ops Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 07/12] drm/xe/xelp: Add AuxCCS invalidation to the indirect context workarounds Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 08/12] drm/xe/display: Move remapped plane loop out of __xe_pin_fb_vma_dpt Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 09/12] drm/xe/display: Change write_dpt_remapped_tiled function signature Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 10/12] drm/xe/display: Respect remapped plane alignment Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 11/12] drm/xe/display: Add support for AuxCCS Tvrtko Ursulin
2026-03-20 17:02 ` [PATCH v24 12/12] drm/xe/xelp: Expose AuxCCS frame buffer modifiers on Alderlake-P Tvrtko Ursulin
2026-03-20 17:07 ` ✗ CI.checkpatch: warning for *AuxCCS handling and render compression modifiers Patchwork
2026-03-20 17:09 ` ✓ CI.KUnit: success " Patchwork
2026-03-20 17:43 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-21 17:52 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-23  9:42   ` Tvrtko Ursulin
2026-03-23 22:11     ` Rodrigo Vivi
2026-03-24  8:25       ` Tvrtko Ursulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-24  8:40 [PATCH v25 00/12] AuxCCS " Tvrtko Ursulin
2026-03-24 18:53 ` ✗ Xe.CI.FULL: failure for " Patchwork
2026-03-19 10:06 [PATCH v23 00/12] " Tvrtko Ursulin
2026-03-20 11:38 ` ✗ Xe.CI.FULL: failure for " Patchwork
2025-12-16 15:37 [PATCH v16 0/8] " Tvrtko Ursulin
2025-12-17 21:57 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-12-08 19:17 [PATCH v15 00/10] " Tvrtko Ursulin
2025-12-09  3:28 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-10-24 10:47 [PATCH v14 00/13] " Tvrtko Ursulin
2025-10-24 23:57 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-11-07 20:55   ` Tvrtko Ursulin
2025-10-20  7:58 [PATCH v13 00/12] " Tvrtko Ursulin
2025-10-20 14:52 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-10-20 15:03   ` Tvrtko Ursulin
2025-01-31 14:20 [PATCH 0/2] " Tvrtko Ursulin
2025-01-31 20:26 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-02-04 11:12   ` Tvrtko Ursulin
2025-02-04 23:36     ` Rodrigo Vivi

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=95dfe41d-e64b-418d-bacb-46d4b0afca7a@igalia.com \
    --to=tvrtko.ursulin@igalia.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@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