From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1423383AbcBQTqJ (ORCPT <rfc822;w@1wt.eu>);
	Wed, 17 Feb 2016 14:46:09 -0500
Received: from bombadil.infradead.org ([198.137.202.9]:52656 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S965253AbcBQTqF (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 17 Feb 2016 14:46:05 -0500
Date: Wed, 17 Feb 2016 20:45:54 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Ross Green <rgkernel@gmail.com>, linux-kernel@vger.kernel.org,
        mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
        akpm@linux-foundation.org,
        Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org,
        dhowells@redhat.com, Eric Dumazet <edumazet@google.com>,
        dvhart@linux.intel.com,
        =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker <fweisbec@gmail.com>,
        oleg@redhat.com, pranith kumar <bobby.prani@gmail.com>
Subject: Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17
Message-ID: <20160217194554.GO6357@twins.programming.kicks-ass.net>
References: <CANfgCY16F5V20Je=50ynZDL+duGVvuRY35tmZ2oi9jBz7Pjp3g@mail.gmail.com>
 <20160217054549.GB6719@linux.vnet.ibm.com>
 <20160217192817.GA21818@linux.vnet.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160217192817.GA21818@linux.vnet.ibm.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 17, 2016 at 11:28:17AM -0800, Paul E. McKenney wrote:
> On Tue, Feb 16, 2016 at 09:45:49PM -0800, Paul E. McKenney wrote:
> > On Tue, Feb 09, 2016 at 09:11:55PM +1100, Ross Green wrote:
> > > Continued testing with the latest linux-4.5-rc3 release.
> > > 
> > > Please find attached a copy of traces from dmesg:
> > > 
> > > There is a lot more debug and trace data so hopefully this will shed
> > > some light on what might be happening here.
> > > 
> > > My testing remains run a series of simple benchmarks, let that run to
> > > completion and then leave the system idle away with just a few daemons
> > > running.
> > > 
> > > the self detected stalls in this instance turned up after a days run time.
> > > There were  NO heavy artificial computational loads on the machine.
> > 
> > It does indeed look quiet on that dmesg for a good long time.
> > 
> > The following insanely crude not-for-mainline hack -might- be producing
> > good results in my testing.  It will take some time before I can claim
> > statistically different results.  But please feel free to give it a go
> > in the meantime.  (Thanks to Al Viro for pointing me in this direction.)

Your case was special in that is was hotplug triggering it, right?

I was auditing the hotplug paths involved when I fell ill two weeks ago,
and have not really made any progress on that because of that :/

I'll go have another look, I had a vague feeling for a race back then,
lets see if I can still remember how..