From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Bhatnagar, Rishabh" <risbhat@amazon.com>
Cc: bigeasy@linutronix.de,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"sashal@kernel.org" <sashal@kernel.org>,
luizcap@amazon.com, abuehaze@amazon.com,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Observing RCU stalls in kernel 5.4/5.10/5.15/6.1 stable trees
Date: Wed, 14 Jun 2023 11:14:49 +0200 [thread overview]
Message-ID: <2023061428-compacter-economic-b648@gregkh> (raw)
In-Reply-To: <c4724b40-89f6-5aa7-720d-c4a4af57cf45@amazon.com>
On Tue, Jun 13, 2023 at 11:58:05AM -0700, Bhatnagar, Rishabh wrote:
>
> On 6/13/23 11:49 AM, Bhatnagar, Rishabh wrote:
> > Hi Sebastian/Greg
> >
> > We are seeing RCU stall warnings from recent stable tree updates:
> > 5.4.243, 5.10.180, 5.15.113, 6.1.31 onwards.
> > This is seen in the upstream stable trees without any downstream patches.
> >
> > The issue is seen few minutes after booting without any workload.
> > We launch hundred's of virtual instances and this shows up in 1-2
> > instances, so its hard to reproduce.
> > Attaching a few stack traces below.
> >
> > The issue can be seen on virtual and baremetal instances.
> > Another interesting point is we only see this on x86 based instances.
> > We also did test this on linux-mainline but were not able to reproduce
> > the issue.
> > So maybe there's a fixup or related commit that has gone in?
Oops, missed this.
Yes, there might be, can you do 'git bisect' and track down the patch
that fixed this?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-14 9:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 18:49 Observing RCU stalls in kernel 5.4/5.10/5.15/6.1 stable trees Bhatnagar, Rishabh
2023-06-13 18:58 ` Bhatnagar, Rishabh
2023-06-14 9:14 ` gregkh
2023-06-14 13:08 ` Luiz Capitulino
2023-06-14 9:14 ` gregkh [this message]
2023-06-14 9:20 ` Sebastian Andrzej Siewior
2023-06-14 13:10 ` Luiz Capitulino
2023-06-14 13:45 ` Sven-Haegar Koch
2023-06-14 13:57 ` Luiz Capitulino
2023-06-14 14:30 ` Mathias Krause
2023-06-15 9:18 ` [PATCH] tick/common: Align tick period during sched_timer setup Sebastian Andrzej Siewior
2023-06-15 9:19 ` kernel test robot
2023-06-15 11:13 ` Mathias Krause
2023-06-15 12:20 ` Richard W.M. Jones
2023-06-15 14:15 ` Luiz Capitulino
2023-06-15 16:00 ` SeongJae Park
2023-06-19 6:18 ` Greg KH
2023-06-19 7:03 ` Mathias Krause
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=2023061428-compacter-economic-b648@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abuehaze@amazon.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luizcap@amazon.com \
--cc=risbhat@amazon.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.