igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-hdmi-a-2 - dmesg-warn - is trying to acquire lock at: down_trylock, but task is already holding lock at: task_call_func
<6> [377.412204] Filesystems sync: 0.002 seconds
<6> [377.412904] Freezing user space processes ...
<4> [377.413156] ------------[ cut here ]------------
<4> [377.413168]
<4> [377.413169] ======================================================
<4> [377.413170] WARNING: possible circular locking dependency detected
<4> [377.413171] 6.1.0-rc1-CI_DRM_12264-g1d6878b45c6d+ #1 Tainted: G U
<4> [377.413172] ------------------------------------------------------
<4> [377.413172] rtcwake/6245 is trying to acquire lock:
<4> [377.413174] ffffffff82735198 ((console_sem).lock){-.-.}-{2:2}, at: down_trylock+0xa/0x30
<4> [377.413182]
but task is already holding lock:
<4> [377.413182] ffff88810c52da60 (&p->pi_lock){-.-.}-{2:2}, at: task_call_func+0x34/0xe0
<4> [377.413188]
which lock already depends on the new lock.
<4> [377.413189]
the existing dependency chain (in reverse order) is:
<4> [377.413189]
-> #1 (&p->pi_lock){-.-.}-{2:2}:
<4> [377.413192] lock_acquire+0xd3/0x310
<4> [377.413195] _raw_spin_lock_irqsave+0x33/0x50
<4> [377.413198] try_to_wake_up+0x6b/0x610
<4> [377.413200] up+0x3b/0x50