From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/guc: Make MMIO communication more robust (rev2)
Date: Mon, 2 Feb 2026 22:34:31 +0100 [thread overview]
Message-ID: <23a33601-f624-49d9-ac05-d6413370a7c7@intel.com> (raw)
In-Reply-To: <28cf2675-88ed-401d-a599-50ec5b16687a@intel.com>
On 1/29/2026 7:57 PM, Michal Wajdeczko wrote:
>
>
> On 1/28/2026 3:54 AM, Patchwork wrote:
>> *Patch Details*
>> *Series:* drm/xe/guc: Make MMIO communication more robust (rev2)
>> *URL:* https://patchwork.freedesktop.org/series/160377/ <https://patchwork.freedesktop.org/series/160377/>
>> *State:* failure
>> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-160377v2/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-160377v2/index.html>
>>
>>
>> CI Bug Log - changes from xe-4456-e8c6d90736933d657ba897686e407f5b9a5058a8_FULL -> xe-pw-160377v2_FULL
>>
>>
>> Summary
>>
>> *FAILURE*
>>
>> Serious unknown changes coming with xe-pw-160377v2_FULL absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in xe-pw-160377v2_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-160377v2_FULL:
>>
>>
>> IGT changes
>>
>>
>> Possible regressions
>>
>> * igt@xe_exec_basic@many-bindexecqueue-userptr@bcs0:
>> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4456-e8c6d90736933d657ba897686e407f5b9a5058a8/shard-bmg-3/igt@xe_exec_basic@many-bindexecqueue-userptr@bcs0.html> -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-160377v2/shard-bmg-1/igt@xe_exec_basic@many-bindexecqueue-userptr@bcs0.html> +1 other test dmesg-fail
>
> <4> [527.456421] xe 0000:03:00.0: [drm] Tile0: GT0: Check job timeout: seqno=4294967292, lrc_seqno=4294967292, guc_id=2, not started
> <4> [532.575325] xe 0000:03:00.0: [drm] Tile0: GT0: Check job timeout: seqno=4294967292, lrc_seqno=4294967292, guc_id=2, not started
> <4> [537.693881] xe 0000:03:00.0: [drm] Tile0: GT0: Check job timeout: seqno=4294967292, lrc_seqno=4294967292, guc_id=2, not started
> <6> [538.335399] xe 0000:03:00.0: [drm] Tile0: GT0: Engine reset: engine_class=bcs, logical_mask: 0x1, guc_id=2, state=0x209
> <5> [538.336026] xe 0000:03:00.0: [drm] Tile0: GT0: Timedout job: seqno=4294967292, lrc_seqno=4294967292, guc_id=2, flags=0x0 in xe_exec_basic [10427]
> <6> [538.360634] xe 0000:03:00.0: [drm] Xe device coredump has been created
>
> but I couldn't reproduce it locally, so lets rerun
>
can't find email with CI.FULL (rev3) results, but they can be found here [1]
[1] https://patchwork.freedesktop.org/series/160377/#rev3
and now the only unrelated 'regression' was in:
* igt@kms_color@ctm-green-to-red@pipe-c-hdmi-a-3:
(kms_color:2305) CRITICAL: Test assertion failure function run_ctm_tests_for_pipe, file ../tests/kms_color.c:835:
next prev parent reply other threads:[~2026-02-02 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:37 [PATCH v2 0/6] drm/xe/guc: Make MMIO communication more robust Michal Wajdeczko
2026-01-27 19:37 ` [PATCH v2 1/6] drm/xe: Promote relaxed_ms_sleep Michal Wajdeczko
2026-01-27 19:46 ` Matthew Brost
2026-01-27 19:37 ` [PATCH v2 2/6] drm/xe: Move exponential sleep logic to helper Michal Wajdeczko
2026-01-27 19:49 ` Matthew Brost
2026-01-27 19:37 ` [PATCH v2 3/6] drm/xe/guc: Limit sleep while waiting for H2G credits Michal Wajdeczko
2026-01-27 19:51 ` Matthew Brost
2026-01-27 19:37 ` [PATCH v2 4/6] drm/xe/guc: Drop redundant register read Michal Wajdeczko
2026-01-27 19:37 ` [PATCH v2 5/6] drm/xe/guc: Wait before retrying sending H2G Michal Wajdeczko
2026-01-27 19:56 ` Matthew Brost
2026-01-27 19:37 ` [PATCH v2 6/6] drm/xe/guc: Allow second H2G retry on FLR Michal Wajdeczko
2026-01-27 19:57 ` Matthew Brost
2026-01-27 19:47 ` ✗ CI.checkpatch: warning for drm/xe/guc: Make MMIO communication more robust (rev2) Patchwork
2026-01-27 19:48 ` ✓ CI.KUnit: success " Patchwork
2026-01-27 20:21 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-28 2:54 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-29 18:57 ` Michal Wajdeczko
2026-02-02 21:34 ` Michal Wajdeczko [this message]
2026-01-29 20:23 ` ✗ CI.checkpatch: warning for drm/xe/guc: Make MMIO communication more robust (rev3) Patchwork
2026-01-29 20:25 ` ✓ CI.KUnit: success " Patchwork
2026-01-29 21:01 ` ✓ Xe.CI.BAT: " Patchwork
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=23a33601-f624-49d9-ac05-d6413370a7c7@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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