From: "Paul E. McKenney" <paulmck@kernel.org>
To: Max Boone <contact@maxboone.com>
Cc: boqun.feng@gmail.com, rcu@vger.kernel.org
Subject: Re: Advice sought on RCU stalls on ARM64 WSL2
Date: Sat, 2 Mar 2024 11:43:42 -0800 [thread overview]
Message-ID: <1a5d96d6-2057-44d9-a4b0-8771c46032fb@paulmck-laptop> (raw)
In-Reply-To: <6a07-65e37700-1-4052b980@161649365>
[ Adding Boqun and the rcu list on CC. ]
On Sat, Mar 02, 2024 at 07:59:08PM +0100, Max Boone wrote:
>
> Dear Dr. McKenney,
>
> For a couple of years now I've been the sometimes frustrated owner of a Microsoft Surface Pro X ARM64 device, which has been getting progressively better as more vendors start targeting their builds at ARM64 architectures but since the introduction of the device there have been issues with the Windows Subsystem for Linux (not more than an opinionated Hyper-V VM with extensive tooling) locking up and hanging.
>
> When this happens, traces like the following are dumped in the kernel messages:
> https://github.com/microsoft/WSL/issues/9454#issuecomment-1942222109
>
> When watching your talk "Decoding Those Inscrutable RCU CPU Stall Warnings" you mentioned one can feel free reaching out when bumping into such issues. Building other kernel releases, switching off-and-on modules and playing with the RCU grace period times so far don't seem to work for me (or others in that thread).
>
> Anyways, I don't really know where to start looking and the call stacks aren't very informative (to my eye) either. I'm hoping you might help me find the direction to look for the root of this problem.
I am assuming that you have filed a bug with the Debian folks, and before
doing that, searched for similar bug reports.
At first glance, this is because things were stuck here:
[ 967.115632] clear_rseq_cs.isra.0+0x4c/0x60
[ 967.116433] do_notify_resume+0xf8/0xeb0
[ 967.116960] el0_svc+0x3c/0x50
[ 967.117537] el0t_64_sync_handler+0x9c/0x120
[ 967.118323] el0t_64_sync+0x158/0x15c
So including these function names (clear_rseq_cs() and so on) in your
search for similar bug reports would be a good idea.
I am unfamiliar with that code.
So I added Boqun because he works with Linux on HyperV as part of his
day job and has a great deal of experience with RCU. He will likely
have quite a number of questions for you including exact versions,
Debian bug number, the results of your web search, and so on. He might
also know an ARM person to get involved in this.
Or maybe he knows the solution off the top of his head!
Thanx, Paul
next parent reply other threads:[~2024-03-02 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a07-65e37700-1-4052b980@161649365>
2024-03-02 19:43 ` Paul E. McKenney [this message]
[not found] ` <3718bb-65e38400-d-5cd53080@68830111>
2024-03-03 0:19 ` Advice sought on RCU stalls on ARM64 WSL2 Paul E. McKenney
2024-03-04 16:33 ` Boqun Feng
2024-03-04 21:54 ` Max Boone
2024-03-05 0:32 ` Joel Fernandes
2024-03-05 5:57 ` Max Boone
2024-03-05 14:32 ` Max Boone
2024-03-05 15:00 ` Joel Fernandes
2024-03-05 14:50 ` Joel Fernandes
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=1a5d96d6-2057-44d9-a4b0-8771c46032fb@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=contact@maxboone.com \
--cc=rcu@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 read-only IMAP folder(s) and NNTP newsgroup(s).