From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761141AbZCTTlu (ORCPT ); Fri, 20 Mar 2009 15:41:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753455AbZCTTll (ORCPT ); Fri, 20 Mar 2009 15:41:41 -0400 Received: from e4.ny.us.ibm.com ([32.97.182.144]:43862 "EHLO e4.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753279AbZCTTlk (ORCPT ); Fri, 20 Mar 2009 15:41:40 -0400 Date: Fri, 20 Mar 2009 12:41:38 -0700 From: "Paul E. McKenney" To: Ingo Molnar Cc: Steven Rostedt , LKML , Thomas Gleixner , Peter Zijlstra , Frederic Weisbecker Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace Message-ID: <20090320194138.GK6698@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20090318031423.981603258@goodmis.org> <20090318055924.GA24627@elte.hu> <20090318073903.GA31341@elte.hu> <20090319073357.GA14615@elte.hu> <20090320174331.GH6698@linux.vnet.ibm.com> <20090320183642.GA2070@elte.hu> <20090320183849.GA3657@elte.hu> <20090320191926.GJ6698@linux.vnet.ibm.com> <20090320192721.GI6224@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090320192721.GI6224@elte.hu> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 20, 2009 at 08:27:21PM +0100, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > On Fri, Mar 20, 2009 at 07:38:49PM +0100, Ingo Molnar wrote: > > > > > > * Ingo Molnar wrote: > > > > > > > > > This looks like it is RCU/stop_machine related. The CPU is > > > > > > stuck in in stop_machine? I see that rcu_torture is running. > > > > > > Does this go away if you turn off rcu_torture? > > > > > > > > > > Grasping at straws... Does Lai's rcu_barrier() fix help? > > > > > > > > which one is that? > > > > > > ok, found it. Will know in about ~24 hours whether it helps. > > > > http://lkml.org/lkml/2009/3/20/71 was the one I was thinking of, > > just to double-check. > > Yeah - i just picked it up into tip:core/rcu. > > I didnt immediately connect the two things, as 'tracer self-test' > does not lend itself to 'CPU hotplug and RCU race fix' - but indeed > in the case of the function tracer there's a dependency due to > stop_machine_run(). Thanks for point it out! Thanks go to Steve Rostedt -- I just followed up on his stack-trace analysis here. ;-) Thanx, Paul