igt@core_hotunplug@subtests - incomplete/dmesg-fail - WARNING: possible recursive locking detected, core_hotunplug.* is trying to acquire lock:, at: intel_pps_lock
<7> [101.448579] xe 0000:00:02.0: [drm:intel_dp_hpd_pulse [xe]] ignoring long hpd on eDP [ENCODER:184:DDI A/PHY A]
<7> [101.572414] xe 0000:00:02.0: [drm:drm_client_release [drm]] drm_fb_helper
<3> [101.646612] DMAR: DRHD: handling fault status reg 3
<3> [101.646685] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x13520f000 [fault reason 0x02] Present bit in context entry is clear
<3> [101.646725] DMAR: DRHD: handling fault status reg 2
<3> [101.646740] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x13483e000 [fault reason 0x02] Present bit in context entry is clear
<3> [101.646809] DMAR: DRHD: handling fault status reg 3
<3> [101.646831] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x110c19000 [fault reason 0x02] Present bit in context entry is clear
<3> [101.646874] DMAR: DRHD: handling fault status reg 2
<7> [101.648381] [IGT] core_hotunplug: late closing removed device instance
<4> [101.651495]
<4> [101.651502] ============================================
<4> [101.651504] WARNING: possible recursive locking detected
<4> [101.651506] 6.9.0-rc1-xe #1 Tainted: G U
<4> [101.651509] --------------------------------------------
<4> [101.651512] core_hotunplug/958 is trying to acquire lock:
<4> [101.651515] ffff88810e1bafd0 (&i915->display.pps.mutex){+.+.}-{3:3}, at: intel_pps_lock+0x2e/0x40 [xe]
<4> [101.651631]
but task is already holding lock:
<4> [101.651634] ffff88810e1bafd0 (&i915->display.pps.mutex){+.+.}-{3:3}, at: intel_pps_lock+0x2e/0x40 [xe]
<4> [101.651700]
other info that might help us debug this:
<4> [101.651703] Possible unsafe locking scenario:
<4> [101.651706] CPU0
<4> [101.651708] ----
<4> [101.651709] lock(&i915->display.pps.mutex);
<4> [101.651713] lock(&i915->display.pps.mutex);
<4> [101.651715]
*** DEADLOCK ***
<4> [101.651718] May be due to missing lock nesting notation
<4> [101.651721] 1 lock held by core_hotunplug/958:
<4> [101.651724] #0: ffff88810e1bafd0 (&i915->display.pps.mutex){+.+.}-{3:3}, at: intel_pps_lock+0x2e/0x40 [xe]
<4> [101.651782]
stack backtrace:
<4> [101.651788] CPU: 0 PID: 958 Comm: core_hotunplug Tainted: G U 6.9.0-rc1-xe #1
<4> [101.651793] Hardware name: Intel Corporation Lunar Lake Client Platform/LNL-M LP5 RVP1, BIOS LNLMFWI1.R00.3093.D84.2403071623 03/07/2024
<4> [101.651799] Call Trace:
<4> [101.651802] <TASK>
<4> [101.651806] dump_stack_lvl+0x9b/0xf0
<4> [101.651815] dump_stack+0x10/0x20
<4> [101.651818] print_deadlock_bug+0x256/0x3a0
<4> [101.651831] __lock_acquire+0x741/0x30a0
<4> [101.651834] ? asm_common_interrupt+0x27/0x40
<4> [101.651841] lock_acquire+0xd7/0x300
<4> [101.651845] ? intel_pps_lock+0x2e/0x40 [xe]
<4> [101.651900] __mutex_lock+0x97/0xe60
<4> [101.651906] ? intel_pps_lock+0x2e/0x40 [xe]
<4> [101.651956] ? __mutex_unlock_slowpath+0x49/0x2d0
<4> [101.651960] ? intel_pps_lock+0x2e/0x40 [xe]
<4> [101.652011] mutex_lock_nested+0x1b/0x30
<4> [101.652014] ? mutex_lock_nested+0x1b/0x30
<4> [101.652017] intel_pps_lock+0x2e/0x40 [xe]
<4> [101.652066] intel_pps_wait_power_cycle+0x2d/0x70 [xe]
<4> [101.652115] intel_dp_encoder_flush_work+0x39/0x60 [xe]
<4> [101.652186] intel_ddi_encoder_destroy+0x35/0xa0 [xe]
<4> [101.652264] drm_mode_config_cleanup+0x4e/0x2e0 [drm]
<4> [101.652320] ? __intel_atomic_global_state_free+0x41/0x70 [xe]
<4> [101.652382] ? intel_atomic_global_obj_cleanup+0xa3/0x120 [xe]
<4> [101.652442] intel_display_driver_remove_noirq+0x5f/0xa0 [xe]
<4> [101.652517] xe_display_fini_noirq+0x21/0x40 [xe]