From: "Paul E. McKenney" <paulmck@kernel.org>
To: frederic@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: TREE01 rcutorture writer stalls?
Date: Tue, 15 Dec 2020 21:04:07 -0800 [thread overview]
Message-ID: <20201216050407.GA14426@paulmck-ThinkPad-P72> (raw)
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Hello, Frederic,
Are you seeing rcutorture writer stalls? Please see attached for an
example from testing, search for "Call Trace". I am running an overnight
test, which should get me some idea of frequency. My thought is to run
on the same version, but without the rcutorture.nocbs_nthreads=0 and
rcutorture.nocbs_toggle=1000 kernel boot parameters.
This sort of error can occur when grace periods are progressing, but
callback processing is not. Things do seem to recover.
Other thoughts?
Thanx, Paul
[-- Attachment #2: console-TREE01.log.gz --]
[-- Type: application/gzip, Size: 140245 bytes --]
next reply other threads:[~2020-12-16 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 5:04 Paul E. McKenney [this message]
2020-12-16 13:01 ` TREE01 rcutorture writer stalls? Frederic Weisbecker
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=20201216050407.GA14426@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).