From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
Joel Fernandes <joelaf@google.com>,
rcu@vger.kernel.org
Subject: Re: [BUG] TREE04 hang on 6.5.y stable: Writer stall state RTWS_COND_SYNC_FULL
Date: Fri, 8 Sep 2023 13:41:26 +0200 [thread overview]
Message-ID: <ZPsIZhhZ1sy/45X+@lothringen> (raw)
In-Reply-To: <0526cf20-7d6f-4e2b-a28e-692ff8bc5955@paulmck-laptop>
On Fri, Sep 08, 2023 at 01:27:06AM -0700, Paul E. McKenney wrote:
> On Thu, Sep 07, 2023 at 08:51:43PM -0400, Joel Fernandes wrote:
> > On Thu, Sep 7, 2023 at 4:03 PM Joel Fernandes <joel@joelfernandes.org> wrote:
> > >
> > >
> > >
> > > > On Sep 7, 2023, at 12:23 PM, Paul E. McKenney <paulmck@kernel.org> wrote:
> > > >
> > > > On Thu, Sep 07, 2023 at 09:17:15AM -0400, Joel Fernandes wrote:
> > > >> Hi,
> > > >> Just started seeing this on 6.5 stable. It is new and first occurrence:
> > > >>
> > > >> TREE04 no success message, 234 successful version messages
> > > >> [033mWARNING: [mTREE04 GP HANG at 14 torture stat 2
> > > >> [ 38.371120] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g1253
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [ 38.388342] Call Trace:
> > > >> [ 53.741039] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g3637
> > > >> f0x2 ->state 0x2 cpu 6
> > > >> [ 69.093462] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g5501
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [ 84.450028] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g10505
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [ 99.815871] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g13781
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [ 115.166476] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g16544
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [ 130.550116] ??? Writer stall state RTWS_COND_SYNC_FULL(10) g18941
> > > >> f0x0 ->state 0x2 cpu 6
> > > >> [..]
> > > >>
> > > >> All logs:
> > > >> http://box.joelfernandes.org:9080/job/rcutorture_stable/job/linux-6.5.y/17/artifact/tools/testing/selftests/rcutorture/res/2023.09.07-04.10.25/TREE04/
> > > >
> > > > Huh. Does this happen for you in v6.5 mainline?
> > > >
> > > > Both the code under test (full-state polled grace periods) and the
> > > > rcutorture test code are fairly new, so there is some reason for general
> > > > suspicion. ;-)
> > >
> > > Ah. I never saw it on either 6.5 mainline or stable till today. Even on stable
> > > I only ever saw it this once. On mainline I have not seen it yet but I do test
> > > stable much more since I have been on stable maintenance duty ;-).
> >
> > I did a couple of long runs and I am not able to reproduce it anymore. :-/
>
> I know that feeling!
Same here, this is after all the reason why we keep the tick dependency within
the hotplug process without really knowing why :o)
next prev parent reply other threads:[~2023-09-08 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 13:17 [BUG] TREE04 hang on 6.5.y stable: Writer stall state RTWS_COND_SYNC_FULL Joel Fernandes
2023-09-07 14:34 ` Paul E. McKenney
2023-09-07 20:03 ` Joel Fernandes
2023-09-08 0:51 ` Joel Fernandes
2023-09-08 8:27 ` Paul E. McKenney
2023-09-08 11:41 ` Frederic Weisbecker [this message]
2023-09-08 13:32 ` Joel Fernandes
2023-09-08 10:28 ` Zhouyi Zhou
2023-09-08 23:33 ` Zhouyi Zhou
2023-09-09 0:10 ` Zhouyi Zhou
2023-09-16 1:09 ` 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=ZPsIZhhZ1sy/45X+@lothringen \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=joelaf@google.com \
--cc=paulmck@kernel.org \
--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 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.