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: Thu, 01 Sep 2022 21:37:01 +0000 [thread overview]
Message-ID: <bug-216388-28872-Gyj0r7lnsG@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 #9 from Robert Dinse (nanook@eskimo.com) ---
I spent some time digging through web server logs, these are the logs from the
machine that produced the last three CPU stall messages, but this time the
stall occurred on apache2, this is cool because that is something I can readily
test. Here is the stall message:
Sep 1 14:26:53 ftp kernel: [ 18.819394][ T298] rcu: INFO: rcu_sched
detected expedited stalls on CPUs/tasks: { 3-... } 4 jiffies s: 441 root: 0x8/.
Sep 1 14:26:53 ftp kernel: [ 18.819413][ T298] rcu: blocking rcu_node
structures (internal RCU debug):
Sep 1 14:26:53 ftp kernel: [ 18.819417][ T298] Task dump for CPU 3:
Sep 1 14:26:53 ftp kernel: [ 18.819418][ T298] task:httpd state:R
running task stack: 0 pid: 2798 ppid: 2460 flags:0x0000400a
Sep 1 14:26:53 ftp kernel: [ 18.819424][ T298] Call Trace:
Sep 1 14:26:53 ftp kernel: [ 18.819428][ T298] <TASK>
Sep 1 14:26:53 ftp kernel: [ 18.819437][ T298] ? alloc_pages+0x90/0x1a0
Sep 1 14:26:53 ftp kernel: [ 18.819443][ T298] ? allocate_slab+0x274/0x460
Sep 1 14:26:53 ftp kernel: [ 18.819445][ T298] ? xa_load+0xa6/0xc0
Sep 1 14:26:53 ftp kernel: [ 18.819448][ T298] ?
___slab_alloc.constprop.0+0x50b/0x5f0
Sep 1 14:26:53 ftp kernel: [ 18.819451][ T298] ?
kmem_cache_alloc_lru+0x297/0x360
Sep 1 14:26:53 ftp kernel: [ 18.819456][ T298] ? nfs_find_actor+0x90/0x90
[nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819504][ T298] ? nfs_alloc_inode+0x21/0x60
[nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819519][ T298] ? alloc_inode+0x23/0xc0
Sep 1 14:26:53 ftp kernel: [ 18.819526][ T298] ?
nfs_alloc_fhandle+0x30/0x30 [nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819541][ T298] ? iget5_locked+0x53/0xa0
Sep 1 14:26:53 ftp kernel: [ 18.819543][ T298] ? list_lru_add+0x13f/0x190
Sep 1 14:26:53 ftp kernel: [ 18.819547][ T298] ? nfs_fhget+0xd2/0x6d0
[nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819570][ T298] ?
nfs_readdir_entry_decode+0x31e/0x440 [nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819581][ T298] ?
nfs_readdir_page_filler+0x10d/0x4f0 [nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819592][ T298] ?
nfs_readdir_xdr_to_array+0x45e/0x4a0 [nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819602][ T298] ? nfs_readdir+0x2e6/0xea0
[nfs]
Sep 1 14:26:53 ftp kernel: [ 18.819613][ T298] ? iterate_dir+0x9b/0x1d0
Sep 1 14:26:53 ftp kernel: [ 18.819615][ T298] ?
__x64_sys_getdents64+0x84/0x120
Sep 1 14:26:53 ftp kernel: [ 18.819616][ T298] ?
__ia32_sys_getdents64+0x120/0x120
Sep 1 14:26:53 ftp kernel: [ 18.819618][ T298] ? do_syscall_64+0x5b/0x80
Sep 1 14:26:53 ftp kernel: [ 18.819620][ T298] ?
do_user_addr_fault+0x1c1/0x620
Sep 1 14:26:53 ftp kernel: [ 18.819622][ T298] ?
exit_to_user_mode_prepare+0x41/0x1e0
Sep 1 14:26:53 ftp kernel: [ 18.819625][ T298] ?
irqentry_exit_to_user_mode+0x9/0x30
Sep 1 14:26:53 ftp kernel: [ 18.819626][ T298] ? irqentry_exit+0x1d/0x30
Sep 1 14:26:53 ftp kernel: [ 18.819627][ T298] ? exc_page_fault+0x86/0x160
Sep 1 14:26:53 ftp kernel: [ 18.819628][ T298] ?
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Sep 1 14:26:53 ftp kernel: [ 18.819631][ T298] </TASK>
Now that process is gone, but the parent process is still running and
Apache still seems to be responding fine. Checking the error log, there were
no errors with that PID.
--
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-01 21: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 [this message]
2022-09-02 5:46 ` bugzilla-daemon
2022-09-02 8:36 ` bugzilla-daemon
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-Gyj0r7lnsG@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).