From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TREE01 rcutorture writer stalls?
Date: Wed, 16 Dec 2020 14:01:14 +0100 [thread overview]
Message-ID: <20201216130114.GA242489@lothringen> (raw)
In-Reply-To: <20201216050407.GA14426@paulmck-ThinkPad-P72>
On Tue, Dec 15, 2020 at 09:04:07PM -0800, Paul E. McKenney wrote:
> 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?
Ok I'm trying to reproduce that.
Thanks.
prev parent reply other threads:[~2020-12-16 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 5:04 TREE01 rcutorture writer stalls? Paul E. McKenney
2020-12-16 13:01 ` Frederic Weisbecker [this message]
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=20201216130114.GA242489@lothringen \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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