Results for igt@xe_exec_fault_mode@invalid-va

Machine description: shard-lnl-6

Result: Fail

i915_display_info7 igt_runner7 results7.json results7-xe-load.json boot7 dmesg7

DetailValue
Duration 1.04 seconds
Hostname 
shard-lnl-6
Igt-Version 
IGT-Version: 1.30-gbd401847a (x86_64) (Linux: 6.14.0-rc4-xe+ x86_64)
Out 
Using IGT_SRANDOM=1740793821 for randomisation
Opened device: /dev/dri/card0
Starting subtest: invalid-va
Stack trace:
  #0 ../lib/igt_core.c:2055 __igt_fail_assert()
  #1 ../tests/intel/xe_exec_fault_mode.c:340 test_exec()
  #2 ../tests/intel/xe_exec_fault_mode.c:504 __igt_unique____real_main401()
  #3 ../tests/intel/xe_exec_fault_mode.c:401 main()
  #4 [__libc_init_first+0x8a]
  #5 [__libc_start_main+0x8b]
  #6 [_start+0x25]
Subtest invalid-va: FAIL (1.037s)
Err 
Starting subtest: invalid-va
(xe_exec_fault_mode:2709) CRITICAL: Test assertion failure function test_exec, file ../tests/intel/xe_exec_fault_mode.c:340:
(xe_exec_fault_mode:2709) CRITICAL: Failed assertion: __xe_wait_ufence(fd, &exec_sync[i], 0xdeadbeefdeadbeefull, exec_queues[i % n_exec_queues], &timeout) == -5
(xe_exec_fault_mode:2709) CRITICAL: Last errno: 62, Timer expired
(xe_exec_fault_mode:2709) CRITICAL: error: -62 != -5
Subtest invalid-va failed.
**** DEBUG ****
(xe_exec_fault_mode:2709) DEBUG: test_exec running on: DRM_XE_ENGINE_CLASS_RENDER
(xe_exec_fault_mode:2709) CRITICAL: Test assertion failure function test_exec, file ../tests/intel/xe_exec_fault_mode.c:340:
(xe_exec_fault_mode:2709) CRITICAL: Failed assertion: __xe_wait_ufence(fd, &exec_sync[i], 0xdeadbeefdeadbeefull, exec_queues[i % n_exec_queues], &timeout) == -5
(xe_exec_fault_mode:2709) CRITICAL: Last errno: 62, Timer expired
(xe_exec_fault_mode:2709) CRITICAL: error: -62 != -5
(xe_exec_fault_mode:2709) igt_core-INFO: Stack trace:
(xe_exec_fault_mode:2709) igt_core-INFO:   #0 ../lib/igt_core.c:2055 __igt_fail_assert()
(xe_exec_fault_mode:2709) igt_core-INFO:   #1 ../tests/intel/xe_exec_fault_mode.c:340 test_exec()
(xe_exec_fault_mode:2709) igt_core-INFO:   #2 ../tests/intel/xe_exec_fault_mode.c:504 __igt_unique____real_main401()
(xe_exec_fault_mode:2709) igt_core-INFO:   #3 ../tests/intel/xe_exec_fault_mode.c:401 main()
(xe_exec_fault_mode:2709) igt_core-INFO:   #4 [__libc_init_first+0x8a]
(xe_exec_fault_mode:2709) igt_core-INFO:   #5 [__libc_start_main+0x8b]
(xe_exec_fault_mode:2709) igt_core-INFO:   #6 [_start+0x25]
****  END  ****
Subtest invalid-va: FAIL (1.037s)
Dmesg
<6> [190.967301] Console: switching to colour dummy device 80x25
<6> [190.967427] [IGT] xe_exec_fault_mode: executing
<6> [190.970417] [IGT] xe_exec_fault_mode: starting subtest invalid-va
<7> [190.973968] xe 0000:00:02.0: [drm:pf_queue_work_func [xe]]
ASID: 149
VFID: 0
PDATA: 0x0490
Faulted Address: 0x0000fffffffff000
FaultType: 0
AccessType: 1
FaultLevel: 3
EngineClass: 0 rcs
EngineInstance: 0
<3> [190.974290] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:321
<3> [190.974322] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2186, name: kworker/u36:10
<3> [190.974331] preempt_count: 1, expected: 0
<3> [190.974335] RCU nest depth: 0, expected: 0
<4> [190.974340] 3 locks held by kworker/u36:10/2186:
<4> [190.974341] #0: ffff88814df36548 ((wq_completion)xe_gt_page_fault_work_queue){+.+.}-{0:0}, at: process_one_work+0x444/0x740
<4> [190.974350] #1: ffffc9000319fe20 ((work_completion)(&pf_queue->worker)){+.+.}-{0:0}, at: process_one_work+0x1da/0x740
<4> [190.974355] #2: ffff888166f5ef68 (&vm->pfs.lock){+.+.}-{2:2}, at: pf_queue_work_func+0x3d3/0x5f0 [xe]
<4> [190.974405] CPU: 1 UID: 0 PID: 2186 Comm: kworker/u36:10 Tainted: G U 6.14.0-rc4-xe+ #1
<4> [190.974407] Tainted: [U]=USER
<4> [190.974407] Hardware name: Intel Corporation Lunar Lake Client Platform/LNL-M LP5 RVP1, BIOS LNLMFWI1.R00.3222.D97.2411281331 11/28/2024
<4> [190.974408] Workqueue: xe_gt_page_fault_work_queue pf_queue_work_func [xe]
<4> [190.974449] Call Trace:
<4> [190.974449] <TASK>
<4> [190.974451] dump_stack_lvl+0xc1/0xf0
<4> [190.974454] dump_stack+0x10/0x20
<4> [190.974456] __might_resched+0x191/0x2e0
<4> [190.974459] __might_sleep+0x58/0xa0
<4> [190.974460] ? pf_queue_work_func+0x418/0x5f0 [xe]
<4> [190.974499] __kmalloc_cache_noprof+0x3a4/0x490
<4> [190.974503] pf_queue_work_func+0x418/0x5f0 [xe]
<4> [190.974541] ? pf_queue_work_func+0x418/0x5f0 [xe]
<4> [190.974579] ? lock_release+0xd4/0x2b0
<4> [190.974583] process_one_work+0x21c/0x740
<4> [190.974587] worker_thread+0x1db/0x3c0
<4> [190.974589] ? __pfx_worker_thread+0x10/0x10
<4> [190.974590] kthread+0x10d/0x270
<4> [190.974592] ? __pfx_kthread+0x10/0x10
<4> [190.974593] ret_from_fork+0x44/0x70
<4> [190.974595] ? __pfx_kthread+0x10/0x10
<4> [190.974596] ret_from_fork_asm+0x1a/0x30
<4> [190.974601] </TASK>
<4> [190.974612]
<4> [190.974636] ============================================
<4> [190.974637] WARNING: possible recursive locking detected
<4> [190.974639] 6.14.0-rc4-xe+ #1 Tainted: G U W
<4> [190.974641] --------------------------------------------
<4> [190.974642] kworker/u36:10/2186 is trying to acquire lock:
<4> [190.974644] ffff888166f5ef68 (&vm->pfs.lock){+.+.}-{2:2}, at: xe_vm_add_pf_entry+0x7d/0x260 [xe]
<4> [190.974723]
but task is already holding lock:
<4> [190.974726] ffff888166f5ef68 (&vm->pfs.lock){+.+.}-{2:2}, at: pf_queue_work_func+0x3d3/0x5f0 [xe]
<4> [190.974801]
other info that might help us debug this:
<4> [190.974804] Possible unsafe locking scenario:
<4> [190.974807] CPU0
<4> [190.974809] ----
<4> [190.974811] lock(&vm->pfs.lock);
<4> [190.974814] lock(&vm->pfs.lock);
<4> [190.974817]
*** DEADLOCK ***
<4> [190.974820] May be due to missing lock nesting notation
<4> [190.974823] 3 locks held by kworker/u36:10/2186:
<4> [190.974826] #0: ffff88814df36548 ((wq_completion)xe_gt_page_fault_work_queue){+.+.}-{0:0}, at: process_one_work+0x444/0x740
<4> [190.974834] #1: ffffc9000319fe20 ((work_completion)(&pf_queue->worker)){+.+.}-{0:0}, at: process_one_work+0x1da/0x740
<4> [190.974842] #2: ffff888166f5ef68 (&vm->pfs.lock){+.+.}-{2:2}, at: pf_queue_work_func+0x3d3/0x5f0 [xe]
<4> [190.974916]
stack backtrace:
<4> [190.974918] CPU: 1 UID: 0 PID: 2186 Comm: kworker/u36:10 Tainted: G U W 6.14.0-rc4-xe+ #1
<4> [190.974920] Tainted: [U]=USER, [W]=WARN
<4> [190.974921] Hardware name: Intel Corporation Lunar Lake Client Platform/LNL-M LP5 RVP1, BIOS LNLMFWI1.R00.3222.D97.2411281331 11/28/2024
<4> [190.974921] Workqueue: xe_gt_page_fault_work_queue pf_queue_work_func [xe]
<4> [190.974986] Call Trace:
<4> [190.974987] <TASK>
<4> [190.974987] dump_stack_lvl+0x91/0xf0
<4> [190.974989] dump_stack+0x10/0x20
<4> [190.974990] print_deadlock_bug+0x23f/0x320
<4> [190.974992] __lock_acquire+0x145f/0x2810
<4> [190.974994] ? mark_held_locks+0x46/0x90
<4> [190.974996] lock_acquire+0xc9/0x300
<4> [190.974998] ? xe_vm_add_pf_entry+0x7d/0x260 [xe]
<4> [190.975070] ? __kmalloc_cache_noprof+0x358/0x490
<4> [190.975072] _raw_spin_lock+0x2f/0x60
<4> [190.975073] ? xe_vm_add_pf_entry+0x7d/0x260 [xe]
<4> [190.975146] xe_vm_add_pf_entry+0x7d/0x260 [xe]
<4> [190.975219] ? __kmalloc_cache_noprof+0x358/0x490
<4> [190.975221] pf_queue_work_func+0x43a/0x5f0 [xe]
<4> [190.975278] ? lock_release+0xd4/0x2b0
<4> [190.975280] process_one_work+0x21c/0x740
<4> [190.975282] worker_thread+0x1db/0x3c0
<4> [190.975284] ? __pfx_worker_thread+0x10/0x10
<4> [190.975285] kthread+0x10d/0x270
<4> [190.975286] ? __pfx_kthread+0x10/0x10
<4> [190.975287] ret_from_fork+0x44/0x70
<4> [190.975288] ? __pfx_kthread+0x10/0x10
<4> [190.975289] ret_from_fork_asm+0x1a/0x30
<4> [190.975292] </TASK>
<6> [192.007345] [IGT] xe_exec_fault_mode: finished subtest invalid-va, FAIL
<6> [192.007548] [IGT] xe_exec_fault_mode: exiting, ret=98
<6> [192.008571] Console: switching to colour frame buffer device 180x56
<6> [192.013479] xe 0000:00:02.0: [drm] GT0: Engine reset: engine_class=rcs, logical_mask: 0x1, guc_id=3
Created at 2025-03-01 02:50:49