From: kernel test robot <oliver.sang@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Petr Mladek <pmladek@suse.com>,
<oliver.sang@intel.com>
Subject: [linus:master] [printk] c158834b22: WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]swapper_is_trying_to_acquire_lock:at:console_lock_spinning_enable_but_task_is_already_holding_lock:at:__report_bad_irq
Date: Fri, 5 Sep 2025 12:44:41 +0800 [thread overview]
Message-ID: <202509051142.70d9ca69-lkp@intel.com> (raw)
Hello,
as we understand, the possible_circular_locking_dependency_detected issue is
not caused by this commit, but has different Call Trace now.
we just make out report FYI what's the WARNING we observed and how it changes
in our tests.
97ea9bccfcbe4c97 c158834b223fbfab3a14855ac20
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
6:12 0% 6:12 dmesg.WARNING:possible_circular_locking_dependency_detected
1:12 -8% :12 dmesg.WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]perf_is_trying_to_acquire_lock:at:console_flush_all_but_task_is_already_holding_lock:at:__report_bad_irq
:12 17% 2:12 dmesg.WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]perf_is_trying_to_acquire_lock:at:console_lock_spinning_enable_but_task_is_already_holding_lock:at:__report_bad_irq
5:12 -42% :12 dmesg.WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]swapper_is_trying_to_acquire_lock:at:console_flush_all_but_task_is_already_holding_lock:at:__report_bad_irq
:12 33% 4:12 dmesg.WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]swapper_is_trying_to_acquire_lock:at:console_lock_spinning_enable_but_task_is_already_holding_lock:at:__report_bad_irq
below full report FYI.
kernel test robot noticed "WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]swapper_is_trying_to_acquire_lock:at:console_lock_spinning_enable_but_task_is_already_holding_lock:at:__report_bad_irq" on:
commit: c158834b223fbfab3a14855ac203b8d9cddbbefd ("printk: nbcon: Use nbcon consoles in console_flush_all()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master d69eb204c255c35abd9e8cb621484e8074c75eaa]
[test failed on linux-next/master 4ac65880ebca1b68495bd8704263b26c050ac010]
in testcase: perf-sanity-tests
version:
with following parameters:
perf_compiler: gcc
group: group-01
config: x86_64-rhel-9.4-bpf
compiler: gcc-12
test machine: 20 threads 1 sockets (Commet Lake) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202509051142.70d9ca69-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250905/202509051142.70d9ca69-lkp@intel.com
kern :warn : [ 429.466465] ======================================================
kern :warn : [ 429.466466] WARNING: possible circular locking dependency detected
kern :warn : [ 429.466467] 6.11.0-rc4-00024-gc158834b223f #1 Not tainted
kern :warn : [ 429.466469] ------------------------------------------------------
kern :warn : [ 429.466470] swapper/17/0 is trying to acquire lock:
kern :warn : [ 429.466472] ffffffff843933c0 (console_owner){-...}-{0:0}, at: console_lock_spinning_enable+0x5b/0x80
kern :warn : [ 429.466480]
but task is already holding lock:
kern :warn : [ 429.466480] ffff8881014fe8c0 (&irq_desc_lock_class){-.-.}-{2:2}, at: __report_bad_irq+0x4f/0xe0
kern :warn : [ 429.466487]
which lock already depends on the new lock.
kern :warn : [ 429.466487]
the existing dependency chain (in reverse order) is:
kern :warn : [ 429.466488]
-> #2 (&irq_desc_lock_class){-.-.}-{2:2}:
kern :warn : [ 429.466492] __lock_acquire+0x760/0xf10
kern :warn : [ 429.466495] lock_acquire+0x148/0x3e0
kern :warn : [ 429.466497] _raw_spin_lock_irqsave+0x38/0x60
kern :warn : [ 429.466500] __irq_get_desc_lock+0x60/0xc0
kern :warn : [ 429.466502] __disable_irq_nosync+0x6a/0xf0
kern :warn : [ 429.466505] disable_hardirq+0xe/0x70
kern :warn : [ 429.466507] e1000_netpoll+0x10e/0x210
kern :warn : [ 429.466511] netpoll_poll_dev+0x162/0x210
kern :warn : [ 429.466515] __netpoll_send_skb+0x2a0/0x3c0
kern :warn : [ 429.466518] write_msg+0x11e/0x160 [netconsole]
kern :warn : [ 429.466524] console_flush_all+0x534/0x640
kern :warn : [ 429.466526] console_unlock+0x88/0x190
kern :warn : [ 429.466528] vprintk_emit+0x1aa/0x1e0
kern :warn : [ 429.466530] _printk+0xb3/0xe0
kern :warn : [ 429.466534] register_console+0x610/0x7e0
kern :warn : [ 429.466536] dns_resolver_preparse+0xfe/0x760 [dns_resolver]
kern :warn : [ 429.466542] do_one_initcall+0xc2/0x400
kern :warn : [ 429.466545] do_init_module+0x13a/0x3e0
kern :warn : [ 429.466548] init_module_from_file+0xcf/0x130
kern :warn : [ 429.466551] idempotent_init_module+0x1b7/0x480
kern :warn : [ 429.466553] __x64_sys_finit_module+0x78/0xd0
kern :warn : [ 429.466555] do_syscall_64+0x8c/0x170
kern :warn : [ 429.466558] entry_SYSCALL_64_after_hwframe+0x76/0x7e
kern :warn : [ 429.466562]
-> #1 (target_list_lock){-...}-{2:2}:
kern :warn : [ 429.466565] __lock_acquire+0x760/0xf10
kern :warn : [ 429.466567] lock_acquire+0x148/0x3e0
kern :warn : [ 429.466570] _raw_spin_lock_irqsave+0x38/0x60
kern :warn : [ 429.466572] write_msg+0x5c/0x160 [netconsole]
kern :warn : [ 429.466577] console_flush_all+0x534/0x640
kern :warn : [ 429.466579] console_unlock+0x88/0x190
kern :warn : [ 429.466581] vprintk_emit+0x1aa/0x1e0
kern :warn : [ 429.466583] _printk+0xb3/0xe0
kern :warn : [ 429.466586] register_console+0x610/0x7e0
kern :warn : [ 429.466588] dns_resolver_preparse+0xfe/0x760 [dns_resolver]
kern :warn : [ 429.466592] do_one_initcall+0xc2/0x400
kern :warn : [ 429.466595] do_init_module+0x13a/0x3e0
kern :warn : [ 429.466597] init_module_from_file+0xcf/0x130
kern :warn : [ 429.466599] idempotent_init_module+0x1b7/0x480
kern :warn : [ 429.466601] __x64_sys_finit_module+0x78/0xd0
kern :warn : [ 429.466604] do_syscall_64+0x8c/0x170
kern :warn : [ 429.466606] entry_SYSCALL_64_after_hwframe+0x76/0x7e
kern :warn : [ 429.466609]
-> #0 (console_owner){-...}-{0:0}:
kern :warn : [ 429.466612] check_prev_add+0x1b1/0x1270
kern :warn : [ 429.466614] validate_chain+0x69e/0x780
kern :warn : [ 429.466616] __lock_acquire+0x760/0xf10
kern :warn : [ 429.466618] lock_acquire+0x148/0x3e0
kern :warn : [ 429.466621] console_lock_spinning_enable+0x77/0x80
kern :warn : [ 429.466623] console_flush_all+0x3a8/0x640
kern :warn : [ 429.466625] console_unlock+0x88/0x190
kern :warn : [ 429.466627] vprintk_emit+0x1aa/0x1e0
kern :warn : [ 429.466629] _printk+0xb3/0xe0
kern :warn : [ 429.466632] __report_bad_irq+0xab/0xe0
kern :warn : [ 429.466635] note_interrupt+0x3e4/0x450
kern :warn : [ 429.466637] handle_irq_event+0xaf/0xc0
kern :warn : [ 429.466639] handle_fasteoi_irq+0xe2/0x3c0
kern :warn : [ 429.466641] __common_interrupt+0x50/0xf0
kern :warn : [ 429.466643] common_interrupt+0x7a/0xa0
kern :warn : [ 429.466646] asm_common_interrupt+0x22/0x40
kern :warn : [ 429.466649] cpuidle_enter_state+0xd2/0x320
kern :warn : [ 429.466652] cpuidle_enter+0x3c/0x60
kern :warn : [ 429.466654] cpuidle_idle_call+0x166/0x1e0
kern :warn : [ 429.466657] do_idle+0xbc/0x130
kern :warn : [ 429.466660] cpu_startup_entry+0x2f/0x40
kern :warn : [ 429.466663] start_secondary+0x1a4/0x1d0
kern :warn : [ 429.466666] common_startup_64+0x13e/0x141
kern :warn : [ 429.466669]
other info that might help us debug this:
kern :warn : [ 429.466670] Chain exists of:
console_owner --> target_list_lock --> &irq_desc_lock_class
kern :warn : [ 429.466674] Possible unsafe locking scenario:
kern :warn : [ 429.466675] CPU0 CPU1
kern :warn : [ 429.466675] ---- ----
kern :warn : [ 429.466676] lock(&irq_desc_lock_class);
kern :warn : [ 429.466678] lock(target_list_lock);
kern :warn : [ 429.466680] lock(&irq_desc_lock_class);
kern :warn : [ 429.466682] lock(console_owner);
kern :warn : [ 429.466683]
*** DEADLOCK ***
kern :warn : [ 429.466684] 3 locks held by swapper/17/0:
kern :warn : [ 429.466685] #0: ffff8881014fe8c0 (&irq_desc_lock_class){-.-.}-{2:2}, at: __report_bad_irq+0x4f/0xe0
kern :warn : [ 429.466692] #1: ffffffff84a93a20 (console_lock){+.+.}-{0:0}, at: vprintk_emit+0x171/0x1e0
kern :warn : [ 429.466697] #2: ffffffff84a93a90 (console_srcu){....}-{0:0}, at: console_flush_all+0x9d/0x640
kern :warn : [ 429.466703]
stack backtrace:
kern :warn : [ 429.466704] CPU: 17 UID: 0 PID: 0 Comm: swapper/17 Not tainted 6.11.0-rc4-00024-gc158834b223f #1
kern :warn : [ 429.466707] Hardware name: Intel Corporation CometLake Client Platform/CometLake S UDIMM (ERB/CRB), BIOS CMLSFWR1.R00.2212.D00.2104290922 04/29/2021
kern :warn : [ 429.466708] Call Trace:
kern :warn : [ 429.466710] <IRQ>
kern :warn : [ 429.466711] dump_stack_lvl+0x62/0x90
kern :warn : [ 429.466716] check_noncircular+0x24d/0x290
kern :warn : [ 429.466719] ? __pfx_check_noncircular+0x10/0x10
kern :warn : [ 429.466723] ? jhash+0x1dc/0x250
kern :warn : [ 429.466728] ? __list_add_valid_or_report+0x33/0xc0
kern :warn : [ 429.466732] ? add_chain_block+0x2dc/0x300
kern :warn : [ 429.466737] check_prev_add+0x1b1/0x1270
kern :warn : [ 429.466742] validate_chain+0x69e/0x780
kern :warn : [ 429.466747] ? __pfx_validate_chain+0x10/0x10
kern :warn : [ 429.466750] ? mark_lock+0x8f/0x520
kern :warn : [ 429.466754] __lock_acquire+0x760/0xf10
kern :warn : [ 429.466760] lock_acquire+0x148/0x3e0
kern :warn : [ 429.466763] ? console_lock_spinning_enable+0x5b/0x80
kern :warn : [ 429.466767] ? __pfx_lock_acquire+0x10/0x10
kern :warn : [ 429.466770] ? do_raw_spin_lock+0x10f/0x1b0
kern :warn : [ 429.466774] ? __pfx_do_raw_spin_lock+0x10/0x10
kern :warn : [ 429.466777] ? console_lock_spinning_enable+0x54/0x80
kern :warn : [ 429.466781] console_lock_spinning_enable+0x77/0x80
kern :warn : [ 429.466784] ? console_lock_spinning_enable+0x5b/0x80
kern :warn : [ 429.466786] console_flush_all+0x3a8/0x640
kern :warn : [ 429.466789] ? console_flush_all+0x9d/0x640
kern :warn : [ 429.466792] ? __pfx_console_flush_all+0x10/0x10
kern :warn : [ 429.466796] ? __pfx_lock_acquire+0x10/0x10
kern :warn : [ 429.466798] ? __pfx_do_raw_spin_lock+0x10/0x10
kern :warn : [ 429.466803] console_unlock+0x88/0x190
kern :warn : [ 429.466805] ? __pfx_console_unlock+0x10/0x10
kern :warn : [ 429.466808] ? do_raw_spin_unlock+0x83/0xf0
kern :warn : [ 429.466812] ? __down_trylock_console_sem+0x82/0x90
kern :warn : [ 429.466815] ? vprintk_emit+0x171/0x1e0
kern :warn : [ 429.466818] vprintk_emit+0x1aa/0x1e0
kern :warn : [ 429.466865] _printk+0xb3/0xe0
kern :warn : [ 429.466868] ? __pfx__printk+0x10/0x10
kern :warn : [ 429.466872] ? common_startup_64+0x13e/0x141
kern :warn : [ 429.466876] ? irq_work_claim+0x1e/0x40
kern :warn : [ 429.466896] __report_bad_irq+0xab/0xe0
kern :warn : [ 429.466900] note_interrupt+0x3e4/0x450
kern :warn : [ 429.466904] handle_irq_event+0xaf/0xc0
kern :warn : [ 429.466907] handle_fasteoi_irq+0xe2/0x3c0
kern :warn : [ 429.466911] __common_interrupt+0x50/0xf0
kern :warn : [ 429.466914] common_interrupt+0x7a/0xa0
kern :warn : [ 429.466917] </IRQ>
kern :warn : [ 429.466918] <TASK>
kern :warn : [ 429.466919] asm_common_interrupt+0x22/0x40
kern :warn : [ 429.466923] RIP: 0010:cpuidle_enter_state+0xd2/0x320
kern :warn : [ 429.466926] Code: bf ff ff ff ff 49 89 c5 e8 1b 72 9d ff 31 ff e8 b4 89 8b fe 45 84 ff 0f 85 c6 01 00 00 e8 f6 6d 9d ff 84 c0 0f 84 ae 01 00 00 <45> 85 e4 0f 88 2d 01 00 00 4d 63 f4 4c 89 ef 4d 6b fe 68 49 01 ef
kern :warn : [ 429.466928] RSP: 0018:ffff8881010bfda8 EFLAGS: 00000202
kern :warn : [ 429.466931] RAX: 000000000066853b RBX: ffffe8ffffc82478 RCX: dffffc0000000000
kern :warn : [ 429.466933] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff829457d5
kern :warn : [ 429.466934] RBP: ffffffff84f2b840 R08: 0000000000000001 R09: 0000000000000001
kern :warn : [ 429.466936] R10: ffffffff854630e7 R11: 0000000000000000 R12: 0000000000000003
kern :warn : [ 429.466938] R13: 00000063f11b8143 R14: 0000000000000003 R15: 0000000000000000
kern :warn : [ 429.466942] ? cpuidle_enter_state+0x285/0x320
kern :warn : [ 429.466945] ? cpuidle_enter_state+0x285/0x320
kern :warn : [ 429.466950] cpuidle_enter+0x3c/0x60
kern :warn : [ 429.466953] cpuidle_idle_call+0x166/0x1e0
kern :warn : [ 429.466957] ? __pfx_cpuidle_idle_call+0x10/0x10
kern :warn : [ 429.466960] ? mark_held_locks+0x24/0x90
kern :warn : [ 429.466963] ? tsc_verify_tsc_adjust+0x77/0x170
kern :warn : [ 429.466967] do_idle+0xbc/0x130
kern :warn : [ 429.466971] cpu_startup_entry+0x2f/0x40
kern :warn : [ 429.466974] start_secondary+0x1a4/0x1d0
kern :warn : [ 429.466978] ? __pfx_start_secondary+0x10/0x10
kern :warn : [ 429.466981] ? startup_64_load_idt+0x93/0xc0
kern :warn : [ 429.466985] common_startup_64+0x13e/0x141
kern :warn : [ 429.466992] </TASK>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-09-05 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 4:44 kernel test robot [this message]
2025-09-05 12:06 ` [linus:master] [printk] c158834b22: WARNING:possible_circular_locking_dependency_detected_kern:warn:[#]swapper_is_trying_to_acquire_lock:at:console_lock_spinning_enable_but_task_is_already_holding_lock:at:__report_bad_irq John Ogness
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202509051142.70d9ca69-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=pmladek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox