✗ CI.KUnit: failure for Tile and GT counting improvements

[Gustavo Sousa]

Quoting Patchwork (2025-07-23 17:26:23-03:00)
>== Series Details ==
>
>Series: Tile and GT counting improvements
>URL   : https://patchwork.freedesktop.org/series/152026/
>State : failure
>
>== Summary ==
>
>+ trap cleanup EXIT
>+ /kernel/tools/testing/kunit/kunit.py run --kunitconfig /kernel/drivers/gpu/drm/xe/.kunitconfig
>stty: 'standard input': Inappropriate ioctl for device
>[20:25:32] Configuring KUnit Kernel ...
>Generating .config ...
>Populating config with:
>$ make ARCH=um O=.kunit olddefconfig
>[20:25:36] Building KUnit Kernel ...
>Populating config with:
>$ make ARCH=um O=.kunit olddefconfig
>Building with:
>$ make all compile_commands.json scripts_gdb ARCH=um O=.kunit --jobs=25
>[20:26:10] Starting KUnit Kernel (1/1)...
>[20:26:10] ============================================================
>Running tests with:
>$ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt
>[20:26:11] ================== guc_buf (11 subtests) ===================
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] stackdepot: allocating hash table of 65536 entries via kvcalloc
>[20:26:11] 
>[20:26:11] Pid: 18, comm: kunit_try_catch Tainted: G        W        N  6.16.0-rc7-gd50fc838d671
>[20:26:11] RIP: 0033:mmio_flush_pending_writes+0x7/0x60
>[20:26:11] RSP: 00000000b988bda8  EFLAGS: 00010206
>[20:26:11] RAX: 0000000000000000 RBX: 000000007b45a3e0 RCX: 0000000000000000
>[20:26:11] RDX: 0000000000000000 RSI: 0000000000101800 RDI: 000000007b45a3e0
>[20:26:11] RBP: 0000000000101800 R08: 0000000000000002 R09: 0000000000000000
>[20:26:11] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000101800
>[20:26:11] R13: 0000000000000001 R14: 0000000060327060 R15: 00000000605a7c20
>[20:26:11] Kernel panic - not syncing: Segfault with no mm
>[20:26:11] [CRASHED] 

Yeah. The issue comes from the fact that, with this patch, we are
probing tile count as part of xe_info_init(), which is used by the kunit
tests.

I'll fix this using the same approach taken for read_gmdid(), i.e., by
using a KUnit static stub.

--
Gustavo Sousa

>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: guc_buf: missing subtest result line!
>[20:26:11] # module: xe
>[20:26:11] ==================== [CRASHED] guc_buf =====================
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] [ERROR] Test: main: missing expected subtest!
>[20:26:11] [CRASHED] 
>[20:26:11] ============================================================
>[20:26:11] Testing complete. Ran 27 tests: crashed: 27, errors: 28
>The kernel seems to have crashed; you can decode the stack traces with:
>$ scripts/decode_stacktrace.sh .kunit/vmlinux .kunit < .kunit/test.log | tee .kunit/decoded.log | /kernel/tools/testing/kunit/kunit.py parse
>[20:26:11] Elapsed time: 38.515s total, 4.248s configuring, 33.849s building, 0.418s running
>
>+ cleanup
>++ stat -c %u:%g /kernel
>+ chown -R 1003:1003 /kernel
>
>