From: Nikolay Borisov <nborisov@suse.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
linux-btrfs@vger.kernel.org
Subject: Re: storm-of-soft-lockups: spinlocks running on all cores, preventing forward progress (4.14- to 5.0+)
Date: Thu, 16 May 2019 09:57:01 +0300 [thread overview]
Message-ID: <0480104e-db25-4e2f-08e5-0236ffd5c1c2@suse.com> (raw)
In-Reply-To: <20190515213650.GG20359@hungrycats.org>
On 16.05.19 г. 0:36 ч., Zygo Blaxell wrote:
> "Storm-of-soft-lockups" is a failure mode where btrfs puts all of the
> CPU cores in kernel functions that are unable to make forward progress,
> but also unwilling to release their respective CPU cores. This is
> usually accompanied by a lot of CPU usage (detectable as either kvm CPU
> usage or just a lot of CPU fan noise) though I don't know if all cores
> are spinning or only some of them.
>
> The kernel console presents a continual stream of "BUG: soft lockup"
> warnings for some days. None of the call traces change during this time.
> The only way out is to reboot.
>
> You can reproduce this by writing a bunch of data to a filesystem while
> bees is running on all cores. It takes a few days to occur naturally.
> It can probably be sped up by just doing a bunch of random LOGICAL_INO
> ioctls in a tight loop on each core.
>
> Here's an instance on a 4-CPU VM where CPU#0 is running btrfs-transaction
> (btrfs_try_tree_write_lock) and CPU#1-3 are running the LOGICAL_INO
> ioctl (btrfs_tree_read_lock_atomic):
Provide output of all sleeping threads when this occur via
echo w > /proc/sysrq-trigger.
Also do you have this patch on the affected machine:
38e3eebff643 ("btrfs: honor path->skip_locking in backref code") can you
try and test with it applied ?
<SNIP>
next prev parent reply other threads:[~2019-05-16 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 21:36 storm-of-soft-lockups: spinlocks running on all cores, preventing forward progress (4.14- to 5.0+) Zygo Blaxell
2019-05-16 6:57 ` Nikolay Borisov [this message]
2019-05-16 16:20 ` Zygo Blaxell
2019-05-18 4:44 ` Zygo Blaxell
2019-05-18 8:27 ` Nikolay Borisov
2019-05-18 21:00 ` Zygo Blaxell
2019-05-18 21:41 ` Zygo Blaxell
2020-02-04 4:57 ` storm-of-soft-lockups: spinlocks running on all cores, preventing forward progress (4.14- to 5.0+, fixed in 5.4) Zygo Blaxell
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=0480104e-db25-4e2f-08e5-0236ffd5c1c2@suse.com \
--to=nborisov@suse.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@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