From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216388] On Host, kernel errors in KVM, on guests, it shows CPU stalls
Date: Fri, 02 Sep 2022 08:36:28 +0000 [thread overview]
Message-ID: <bug-216388-28872-sA4Q9o1QVN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216388-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216388
--- Comment #11 from Robert Dinse (nanook@eskimo.com) ---
Well still happening with gcc-12.2.0 but seems to be somewhat less frequent.
[ 7.092312] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: {
4-... } 3 jiffies s: 389 root: 0x10/.
[ 7.092329] rcu: blocking rcu_node structures (internal RCU debug):
[ 7.092332] Task dump for CPU 4:
[ 7.092334] task:modprobe state:R running task stack: 0 pid:
1502 ppid: 8 flags:0x0000400a
[ 7.092338] Call Trace:
[ 7.092344] <TASK>
[ 7.092347] ? __wake_up_common_lock+0x87/0xc0
[ 7.092355] ? sysvec_apic_timer_interrupt+0x90/0xa0
[ 7.092361] ? insn_get_prefixes+0x1f1/0x440
[ 7.092365] ? load_new_mm_cr3+0x7f/0xe0
[ 7.092368] ? cpumask_any_but+0x35/0x50
[ 7.092372] ? x2apic_send_IPI_allbutself+0x2f/0x40
[ 7.092375] ? do_sync_core+0x2a/0x30
[ 7.092379] ? cpumask_next+0x23/0x30
[ 7.092381] ? smp_call_function_many_cond+0xea/0x370
[ 7.092386] ? text_poke_memset+0x20/0x20
[ 7.092389] ? arch_unregister_cpu+0x50/0x50
[ 7.092394] ? __fscache_acquire_cookie+0x4f4/0x500 [fscache]
[ 7.092407] ? on_each_cpu_cond_mask+0x1d/0x30
[ 7.092409] ? text_poke_bp_batch+0xaf/0x210
[ 7.092412] ? __traceiter_fscache_volume+0x60/0x60 [fscache]
[ 7.092421] ? __fscache_acquire_cookie+0x4f4/0x500 [fscache]
[ 7.092429] ? __fscache_acquire_cookie+0x4f4/0x500 [fscache]
[ 7.092438] ? text_poke_bp+0x49/0x70
[ 7.092440] ? __static_call_transform+0x7f/0x120
[ 7.092442] ? arch_static_call_transform+0x87/0xa0
[ 7.092446] ? __static_call_init+0x167/0x210
[ 7.092450] ? static_call_module_notify+0x13e/0x1a0
[ 7.092452] ? blocking_notifier_call_chain_robust+0x72/0xd0
[ 7.092456] ? load_module+0x2068/0x25e0
[ 7.092459] ? ima_post_read_file+0xd5/0x100
[ 7.092464] ? __do_sys_finit_module+0xbd/0x130
[ 7.092466] ? __do_sys_finit_module+0xbd/0x130
[ 7.092469] ? __x64_sys_finit_module+0x18/0x20
[ 7.092470] ? do_syscall_64+0x5b/0x80
[ 7.092474] ? ksys_mmap_pgoff+0x108/0x250
[ 7.092478] ? do_syscall_64+0x67/0x80
[ 7.092480] ? exit_to_user_mode_prepare+0x41/0x1e0
[ 7.092485] ? syscall_exit_to_user_mode+0x1b/0x40
[ 7.092487] ? do_syscall_64+0x67/0x80
[ 7.092489] ? do_syscall_64+0x67/0x80
[ 7.092492] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 7.092496] </TASK>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-09-02 8:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 7:37 [Bug 216388] New: On Host, kernel errors in KVM, on guests, it shows CPU stalls bugzilla-daemon
2022-08-22 17:50 ` Sean Christopherson
2022-08-22 23:21 ` Zhenyu Wang
2022-08-22 17:50 ` [Bug 216388] " bugzilla-daemon
2022-08-22 23:46 ` bugzilla-daemon
2022-08-23 0:57 ` bugzilla-daemon
2022-08-27 19:42 ` bugzilla-daemon
2022-08-28 21:08 ` bugzilla-daemon
2022-09-01 6:09 ` bugzilla-daemon
2022-09-01 16:44 ` Sean Christopherson
2022-09-01 16:44 ` bugzilla-daemon
2022-09-01 19:46 ` bugzilla-daemon
2022-09-01 21:37 ` bugzilla-daemon
2022-09-02 5:46 ` bugzilla-daemon
2022-09-02 8:36 ` bugzilla-daemon [this message]
2022-09-03 1:37 ` bugzilla-daemon
2022-09-03 2:03 ` bugzilla-daemon
2022-09-03 5:31 ` bugzilla-daemon
2022-09-03 5:37 ` bugzilla-daemon
2022-09-06 15:52 ` Sean Christopherson
2022-09-04 4:17 ` bugzilla-daemon
2022-09-04 5:41 ` bugzilla-daemon
2022-09-05 4:06 ` bugzilla-daemon
2022-09-06 15:52 ` bugzilla-daemon
2022-09-06 21:44 ` bugzilla-daemon
2022-09-17 19:53 ` bugzilla-daemon
2022-09-17 20:23 ` bugzilla-daemon
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=bug-216388-28872-sA4Q9o1QVN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).