Few tests - abort - ((work_completion)(&(&guc->timestamp.work)->work)){+.+.}-{0:0}, at: process_one_work
<6> [239.278070] Console: switching to colour dummy device 80x25
<6> [239.278160] [IGT] gem_create: executing
<7> [239.280622] i915 0000:00:02.0: [drm:i915_gem_open [i915]]
<7> [239.281014] i915 0000:00:02.0: [drm:i915_drop_caches_set [i915]] Dropping caches: 0x0000005c [0x0000005c]
<7> [239.281171] i915 0000:00:02.0: [drm:i915_gem_open [i915]]
<6> [239.284031] [IGT] gem_create: starting subtest busy-create
<6> [239.284137] [IGT] gem_create: starting dynamic subtest smem0
<7> [239.284342] [drm:eb_lookup_vmas [i915]] EINVAL at eb_validate_vma:508
<4> [267.634431]
<4> [267.634438] ======================================================
<4> [267.634441] WARNING: possible circular locking dependency detected
<4> [267.634443] 6.4.0-rc1-CI_DRM_13139-g978798460589+ #1 Not tainted
<4> [267.634445] ------------------------------------------------------
<4> [267.634447] kworker/2:1H/119 is trying to acquire lock:
<4> [267.634449] ffff88811030cf30 (>->reset.backoff_srcu){++++}-{0:0}, at: _intel_gt_reset_lock+0x0/0x330 [i915]
<4> [267.634654]
but task is already holding lock:
<4> [267.634656] ffffc900005abe60 ((work_completion)(&(&guc->timestamp.work)->work)){+.+.}-{0:0}, at: process_one_work+0x1cc/0x510
<4> [267.634664]
which lock already depends on the new lock.
<4> [267.634667]
the existing dependency chain (in reverse order) is:
<4> [267.634669]
-> #3 ((work_completion)(&(&guc->timestamp.work)->work)){+.+.}-{0:0}:
<4> [267.634673] lock_acquire+0xd8/0x2d0
<4> [267.634678] __flush_work+0x74/0x530
<4> [267.634680] __cancel_work_timer+0x14f/0x1f0
<4> [267.634683] intel_guc_submission_reset_prepare+0x81/0x4b0 [i915]
<4> [267.634817] intel_uc_reset_prepare+0x9c/0x120 [i915]
<4> [267.634942] reset_prepare+0x21/0x60 [i915]