From: Joel Fernandes <joelaf@google.com>
To: rcu@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>
Subject: [BUG] TREE04 hang on 6.5.y stable: Writer stall state RTWS_COND_SYNC_FULL
Date: Thu, 7 Sep 2023 09:17:15 -0400 [thread overview]
Message-ID: <CAJWu+ooLBjAhZbHa+64egmh53-n7qc_o+PvsfSt2hzQNrVhdqw@mail.gmail.com> (raw)
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/
thanks,
- Joel
next reply other threads:[~2023-09-07 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 13:17 Joel Fernandes [this message]
2023-09-07 14:34 ` [BUG] TREE04 hang on 6.5.y stable: Writer stall state RTWS_COND_SYNC_FULL 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
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=CAJWu+ooLBjAhZbHa+64egmh53-n7qc_o+PvsfSt2hzQNrVhdqw@mail.gmail.com \
--to=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 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).