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: Sat, 27 Aug 2022 19:42:34 +0000 [thread overview]
Message-ID: <bug-216388-28872-Bw2DeK04yH@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 #4 from Robert Dinse (nanook@eskimo.com) ---
I am not seeing this particular CPU stall on 5.19.4, but I am seeing other
CPU stalls. I've opened three different tickets on CPU stalls because they've
all been in completely different tasks but at this point I have to wonder if
there isn't some common code that they are all calling or a broken structure
they are all using or something similar. Rather than open 40 more tickets that
all end up being a duplicate, perhaps someone familiar with the internal
workings could look at these two tickets in addition to this one, #216399,
which is a stall on an MDRAID task, and #216405, and then before I open yet
another ticket, here is yet another CPU stall in a task worker:
[ 489.383957] INFO: task worker:11403 blocked for more than 122 seconds.
[ 489.383962] Not tainted 5.19.4 #1
[ 489.383964] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 489.383965] task:worker state:D stack: 0 pid:11403 ppid: 1
flags:0x00004002
[ 489.383968] Call Trace:
[ 489.383970] <TASK>
[ 489.383973] __schedule+0x367/0x1400
[ 489.383980] schedule+0x58/0xf0
[ 489.383983] io_schedule+0x46/0x80
[ 489.383985] folio_wait_bit_common+0x11e/0x350
[ 489.383989] ? filemap_invalidate_unlock_two+0x50/0x50
[ 489.383992] folio_wait_bit+0x18/0x20
[ 489.383994] folio_wait_writeback+0x2c/0x80
[ 489.383997] wait_on_page_writeback+0x18/0x50
[ 489.383999] __filemap_fdatawait_range+0x98/0x140
[ 489.384003] file_write_and_wait_range+0x83/0xb0
[ 489.384005] ext4_sync_file+0xf3/0x320
[ 489.384009] __x64_sys_fdatasync+0x4e/0xa0
[ 489.384012] ? syscall_enter_from_user_mode+0x50/0x70
[ 489.384014] do_syscall_64+0x58/0x80
[ 489.384017] ? sysvec_apic_timer_interrupt+0x4b/0xa0
[ 489.384020] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 489.384022] RIP: 0033:0x7f96e331bb1b
[ 489.384025] RSP: 002b:00007f96788c75d0 EFLAGS: 00000293 ORIG_RAX:
000000000000004b
[ 489.384027] RAX: ffffffffffffffda RBX: 00005639414e0860 RCX:
00007f96e331bb1b
[ 489.384029] RDX: 0000000000000000 RSI: 0000000000000000 RDI:
000000000000000b
[ 489.384030] RBP: 0000563941270890 R08: 0000000000000000 R09:
0000000000000000
[ 489.384031] R10: 00007f96788c75f0 R11: 0000000000000293 R12:
0000000000000000
[ 489.384033] R13: 00005639412708f8 R14: 00005639425cedd0 R15:
00007ffded76f3d0
[ 489.384036] </TASK>
If this appears to be related I will not generate a ticket but I am not
knowledgable enough about the internals to know.
--
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-08-27 19:42 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 [this message]
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
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-Bw2DeK04yH@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).