Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Mallesh Koujalagi" <mallesh.koujalagi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ Xe.CI.BAT: failure for drm/xe/sysctrl: Clean up error handling in (rev6)
Date: Mon, 21 Sep 2026 14:54:03 -0000	[thread overview]
Message-ID: <179000244355.188107.1726647021680638734@61270ab9df2a> (raw)
In-Reply-To: <20260921133927.128281-12-mallesh.koujalagi@intel.com>

[-- Attachment #1: Type: text/plain, Size: 4958 bytes --]

== Series Details ==

Series: drm/xe/sysctrl: Clean up error handling in (rev6)
URL   : https://patchwork.freedesktop.org/series/172513/
State : failure

== Summary ==

CI Bug Log - changes from xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb_BAT -> xe-pw-172513v6_BAT
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with xe-pw-172513v6_BAT absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in xe-pw-172513v6_BAT, 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 (15 -> 15)
------------------------------

  No changes in participating hosts

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in xe-pw-172513v6_BAT:

### IGT changes ###

#### Possible regressions ####

  * igt@xe_exec_fault_mode@twice-basic:
    - bat-bmg-1:          [PASS][1] -> [DMESG-WARN][2] +2 other tests dmesg-warn
   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-1/igt@xe_exec_fault_mode@twice-basic.html
   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-1/igt@xe_exec_fault_mode@twice-basic.html

  * igt@xe_exec_system_allocator@many-execqueues-free:
    - bat-bmg-vm:         [PASS][3] -> [DMESG-WARN][4]
   [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-vm/igt@xe_exec_system_allocator@many-execqueues-free.html
   [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-vm/igt@xe_exec_system_allocator@many-execqueues-free.html

  * igt@xe_multigpu_svm@mgpu-latency-copy-prefetch:
    - bat-bmg-3:          [PASS][5] -> [DMESG-WARN][6]
   [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-3/igt@xe_multigpu_svm@mgpu-latency-copy-prefetch.html
   [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-3/igt@xe_multigpu_svm@mgpu-latency-copy-prefetch.html

  
Known issues
------------

  Here are the changes found in xe-pw-172513v6_BAT that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@core_hotunplug@unbind-rebind:
    - bat-bmg-2:          [PASS][7] -> [ABORT][8] ([Intel XE#8007])
   [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-2/igt@core_hotunplug@unbind-rebind.html
   [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-2/igt@core_hotunplug@unbind-rebind.html

  * igt@xe_waitfence@engine:
    - bat-ptl-2:          [PASS][9] -> [FAIL][10] ([Intel XE#9109])
   [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-ptl-2/igt@xe_waitfence@engine.html
   [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-ptl-2/igt@xe_waitfence@engine.html

  
#### Possible fixes ####

  * igt@xe_exec_system_allocator@many-execqueues-malloc:
    - bat-bmg-vm:         [DMESG-WARN][11] -> [PASS][12] +1 other test pass
   [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-vm/igt@xe_exec_system_allocator@many-execqueues-malloc.html
   [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-vm/igt@xe_exec_system_allocator@many-execqueues-malloc.html

  * igt@xe_exec_system_allocator@threads-shared-vm-many-malloc:
    - bat-bmg-1:          [DMESG-WARN][13] -> [PASS][14] +1 other test pass
   [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-1/igt@xe_exec_system_allocator@threads-shared-vm-many-malloc.html
   [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-1/igt@xe_exec_system_allocator@threads-shared-vm-many-malloc.html

  * igt@xe_multigpu_svm@mgpu-pagefault-basic:
    - bat-bmg-3:          [DMESG-WARN][15] -> [PASS][16]
   [15]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb/bat-bmg-3/igt@xe_multigpu_svm@mgpu-pagefault-basic.html
   [16]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/bat-bmg-3/igt@xe_multigpu_svm@mgpu-pagefault-basic.html

  
  [Intel XE#8007]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8007
  [Intel XE#9109]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/9109


Build changes
-------------

  * Linux: xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb -> xe-pw-172513v6

  IGT_9103: f307fd753abbe6c03d0a6e1c769fc6020ebd5d86 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  xe-5795-f709158f7998ec6a0c6ecebe5aa7911bfb8412bb: f709158f7998ec6a0c6ecebe5aa7911bfb8412bb
  xe-pw-172513v6: 172513v6

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-172513v6/index.html

[-- Attachment #2: Type: text/html, Size: 5759 bytes --]

  parent reply	other threads:[~2026-09-21 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 13:39 [PATCH v8 00/10] drm/xe/sysctrl: Clean up error handling in Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 01/10] drm/xe/sysctrl: Return error codes from sysctrl_wait_bit_clear() Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 02/10] drm/xe/sysctrl: Return error codes from sysctrl_wait_bit_set() Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 03/10] drm/xe/sysctrl: Make sysctrl_write_frame() void Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 04/10] drm/xe/sysctrl: Make sysctrl_read_frame() void Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 05/10] drm/xe/sysctrl: Use xe_assert() for payload size validation Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 06/10] drm/xe/sysctrl: simplify mailbox header handling Mallesh Koujalagi
2026-09-22 11:17   ` Michal Wajdeczko
2026-09-23 10:54     ` Mallesh, Koujalagi
2026-09-24  5:34     ` Anoop Vijay
2026-09-23 23:52   ` Umesh Nerlige Ramappa
2026-09-21 13:39 ` [PATCH v8 07/10] drm/xe/sysctrl: Replace FIELD_GET() with REG_FIELD_GET() Mallesh Koujalagi
2026-09-22 11:11   ` Michal Wajdeczko
2026-09-21 13:39 ` [PATCH v8 08/10] drm/xe/sysctrl: Improve firmware response error logging Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 09/10] drm/xe/sysctrl: Log group and command ID on mailbox failure Mallesh Koujalagi
2026-09-21 13:39 ` [PATCH v8 10/10] drm/xe/sysctrl: Report 'System Controller event' error using SIGID Mallesh Koujalagi
2026-09-21 13:48 ` ✓ CI.KUnit: success for drm/xe/sysctrl: Clean up error handling in (rev6) Patchwork
2026-09-21 14:54 ` Patchwork [this message]
2026-09-21 20:02 ` ✗ Xe.CI.FULL: failure " 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=179000244355.188107.1726647021680638734@61270ab9df2a \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@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