igt@i915_pm_rpm@gem-execbuf@smem0 - incomplete - pstore logs - is trying to acquire lock at: down_trylock, but task is already holding lock at: try_to_wake_up
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7607/shard-iclb4/igt@i915_pm_rpm@gem-execbuf@smem0.html https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7607/shard-iclb4/pstore22-1659719216_Panic_1.txt
<4>[ 198.990356] ------------[ cut here ]------------
<4>[ 198.990371]
<4>[ 198.990371] ======================================================
<4>[ 198.990372] WARNING: possible circular locking dependency detected
<4>[ 198.990372] 5.19.0-CI_DRM_11969-g7cd3fde3b35a+ #1 Not tainted
<4>[ 198.990373] ------------------------------------------------------
<4>[ 198.990373] kworker/3:2/405 is trying to acquire lock:
<4>[ 198.990374] ffffffff82734dd8 ((console_sem).lock){-.-.}-{2:2}, at: down_trylock+0xa/0x30
<4>[ 198.990380]
<4>[ 198.990380] but task is already holding lock:
<4>[ 198.990381] ffff8881082b0908 (&p->pi_lock){-.-.}-{2:2}, at: try_to_wake_up+0x6b/0x830
<4>[ 198.990384]
<4>[ 198.990384] which lock already depends on the new lock.
<4>[ 198.990384]
<4>[ 198.990384]
<4>[ 198.990384] the existing dependency chain (in reverse order) is:
<4>[ 198.990384]
<4>[ 198.990384] -> #1 (&p->pi_lock){-.-.}-{2:2}:
<4>[ 198.990386] _raw_spin_lock_irqsave+0x33/0x50
<4>[ 198.990389] try_to_wake_up+0x6b/0x830
<4>[ 198.990390] up+0x3b/0x50
<4>[ 198.990391] __up_console_sem+0x5c/0x70
<4>[ 198.990393] console_unlock+0x1bc/0x1d0
<4>[ 198.990395] vprintk_emit+0x251/0x380
<4>[ 198.990396] _printk+0x53/0x6e
<4>[ 198.990398] do_exit.cold.43+0x3d/0x48
<4>[ 198.990399] do_group_exit+0x2e/0xb0
<4>[ 198.990401] __x64_sys_exit_group+0xf/0x10
<4>[ 198.990402] do_syscall_64+0x37/0x90
<4>[ 198.990404] entry_SYSCALL_64_after_hwframe+0x63/0xcd
<4>[ 198.990405]
<4>[ 198.990405] -> #0 ((console_sem).lock){-.-.}-{2:2}:
<4>[ 198.990406] __lock_acquire+0x15b1/0x2950
<4>[ 198.990409] lock_acquire+0xd3/0x310
<4>[ 198.990410] _raw_spin_lock_irqsave+0x33/0x50
<4>[ 198.990411] down_trylock+0xa/0x30
<4>[ 198.990413] __down_trylock_console_sem+0x25/0xb0
<4>[ 198.990414] console_trylock+0xe/0x70
<4>[ 198.990416] vprintk_emit+0x13c/0x380
<4>[ 198.990417] _printk+0x53/0x6e
<4>[ 198.990418] report_bug.cold.2+0x10/0x52
<4>[ 198.990420] handle_bug+0x3f/0x70
<4>[ 198.990421] exc_invalid_op+0x13/0x60
<4>[ 198.990422] asm_exc_invalid_op+0x16/0x20
<4>[ 198.990423] set_task_cpu+0x286/0x2a0
<4>[ 198.990424] try_to_wake_up+0x1a5/0x830
<4>[ 198.990425] autoremove_wake_function+0xc/0x50
<4>[ 198.990426] __wake_up_common+0x81/0x1b0
<4>[ 198.990427] __wake_up_common_lock+0x75/0xb0
<4>[ 198.990428] ep_poll_callback+0xcf/0x4e0
<4>[ 198.990430] __wake_up_common+0x81/0x1b0
<4>[ 198.990431] __wake_up_common_lock+0x75/0xb0
<4>[ 198.990432] sock_def_readable+0x77/0x290
<4>[ 198.990434] __netlink_sendskb+0x32/0x50
<4>[ 198.990436] netlink_broadcast+0x3ce/0x490
<4>[ 198.990437] kobject_uevent_env+0x3e1/0x790
<4>[ 198.990439] device_del+0x2b6/0x410
<4>[ 198.990441] cdev_device_del+0x10/0x30
<4>[ 198.990444] bsg_unregister_queue+0x38/0x50
<4>[ 198.990446] __scsi_remove_device+0xe5/0x140
<4>[ 198.990448] scsi_remove_device+0x1e/0x30
<4>[ 198.990450] ata_scsi_handle_link_detach.cold.40+0x2a/0x37
<4>[ 198.990453] ata_scsi_hotplug+0x3d/0x90
<4>[ 198.990454] process_one_work+0x272/0x5c0
<4>[ 198.990456] worker_thread+0x37/0x370
<4>[ 198.990457] kthread+0xed/0x120
<4>[ 198.990458] ret_from_fork+0x1f/0x30
<4>[ 198.990460]
<4>[ 198.990460] other info that might help us debug this:
<4>[ 198.990460]
<4>[ 198.990460] Possible unsafe locking scenario:
<4>[ 198.990460]
<4>[ 198.990460] CPU0 CPU1
<4>[ 198.990460] ---- ----
<4>[ 198.990461] lock(&p->pi_lock);
<4>[ 198.990461] lock((console_sem).lock);
<4>[ 198.990462] lock(&p->pi_lock);
<4>[ 198.990463] lock((console_sem).lock);
<4>[ 198.990463]
<4>[ 198.990463] *** DEADLOCK ***
Edited by LAKSHMINARAYANA VUDUM