From: Luis Chamberlain <mcgrof@kernel.org>
To: mst@redhat.com, david@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>
Cc: Luis Chamberlain <mcgrof@kernel.org>, linux-kernel@vger.kernel.org
Subject: update_balloon_size_func blocked for more than 120 seconds
Date: Thu, 11 Nov 2021 14:48:25 -0800 [thread overview]
Message-ID: <YY2duTi0wAyAKUTJ@bombadil.infradead.org> (raw)
I get the following splats with a kvm guest in idle, after a few seconds
it starts:
[ 242.412806] INFO: task kworker/6:2:271 blockedfor more than 120 seconds.
[ 242.415790] Tainted: G E 5.15.0-next-20211111 #68
[ 242.417755] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 242.418332] task:kworker/6:2 state:D stack: 0 pid: 271 ppid: 2 flags:0x00004000
[ 242.418954] Workqueue: events_freezable update_balloon_size_func [virtio_balloon]
[ 242.419518] Call Trace:
[ 242.419709] <TASK>
[ 242.419873] __schedule+0x2fd/0x990
[ 242.420142] schedule+0x4e/0xc0
[ 242.420382] tell_host+0xaa/0xf0 [virtio_balloon]
[ 242.420757] ? do_wait_intr_irq+0xa0/0xa0
[ 242.421065] update_balloon_size_func+0x2c9/0x2e0 [virtio_balloon]
[ 242.421527] process_one_work+0x1e5/0x3c0
[ 242.421833] worker_thread+0x50/0x3b0
[ 242.422204] ? rescuer_thread+0x370/0x370
[ 242.422507] kthread+0x169/0x190
[ 242.422754] ? set_kthread_struct+0x40/0x40
[ 242.423073] ret_from_fork+0x1f/0x30
[ 242.423347] </TASK>
And this goes on endlessly. The last one says it blocked for more than 1208
seconds. This was not happening until the last few weeks but I see no
relevant recent commits for virtio_balloon, so the related change could
be elsewhere.
I could bisect but first I figured I'd check to see if someone already
had spotted this.
Luis
next reply other threads:[~2021-11-11 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 22:48 Luis Chamberlain [this message]
2021-11-12 9:13 ` update_balloon_size_func blocked for more than 120 seconds David Hildenbrand
2021-11-24 1:32 ` Michael Ellerman
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=YY2duTi0wAyAKUTJ@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=vbabka@suse.cz \
--cc=virtualization@lists.linux-foundation.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).