Received-SPF: pass (google.com: domain of linux-kernel+bounces-18731-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Sat, 6 Jan 2024 23:36:03 +0100
From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Prototype patch to avoid TREE07 rcu_torture_writer() stalls
Message-ID: <ZZnV0xt9ZhAu-vUh@localhost.localdomain>
References: <a40344c8-a260-41f3-bd7a-6a63d8660489@paulmck-laptop>
 <ZZiIQvu+2CGufvOL@lothringen>
 <3da2e014-ed54-4b2a-9fde-99d6eef3e897@paulmck-laptop>
 <8c135e1a-5f66-42ae-9749-71a65f86dcbf@paulmck-laptop>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8c135e1a-5f66-42ae-9749-71a65f86dcbf@paulmck-laptop>

Le Sat, Jan 06, 2024 at 06:55:14AM -0800, Paul E. McKenney a ?crit :
> > Is this related?
> > 
> > But then the system picks itself up, dusts itself off, and goes along
> > as if nothing had happened.
> > 
> > Maybe a long-running IRQ, NMI, or SMI?
> 
> Or, based on a recent bug chase of another type, high contention on
> an IRQ-disabled spinlock?

Before checking the guest's dmesg, I should probably have checked the host's.
It seems to report some softlockups, perhaps due to too many instances
in parallel where memory is not that generous.

Let me try to run as much time (250 hours) but with fewer instances in
parallel.

Thanks.