From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757789AbYJIHeS (ORCPT ); Thu, 9 Oct 2008 03:34:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755943AbYJIHeH (ORCPT ); Thu, 9 Oct 2008 03:34:07 -0400 Received: from www.tglx.de ([62.245.132.106]:58423 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755635AbYJIHeF (ORCPT ); Thu, 9 Oct 2008 03:34:05 -0400 Date: Thu, 9 Oct 2008 09:24:51 +0200 (CEST) From: Thomas Gleixner To: Andi Kleen cc: "Paul E. McKenney" , mingo@elte.hu, linux-kernel@vger.kernel.org, rjw@sisk.pl, dipankar@in.ibm.com Subject: Re: RCU hang on cpu re-hotplug with 2.6.27rc8 In-Reply-To: <20081009045646.GB24560@one.firstfloor.org> Message-ID: References: <20081006141220.GA14160@basil.nowhere.org> <20081006232837.GA1157@basil.nowhere.org> <20081007030822.GC6820@linux.vnet.ibm.com> <20081007071544.GC20740@one.firstfloor.org> <20081007152629.GH6384@linux.vnet.ibm.com> <20081007154939.GN20740@one.firstfloor.org> <20081007163401.GJ6384@linux.vnet.ibm.com> <20081007210947.GP20740@one.firstfloor.org> <20081007212215.GN6384@linux.vnet.ibm.com> <20081009013321.GA11291@linux.vnet.ibm.com> <20081009045646.GB24560@one.firstfloor.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 9 Oct 2008, Andi Kleen wrote: > It actually does. The stall detector makes the online echo return after three seconds, > although it's not 100% clear to me why. > > here's the backtrace > > RCU detected CPU 14 stall (t=4295149800/5928 jiffies) > Pid: 0, comm: swapper Not tainted 2.6.27-rc9 #5 > > Call Trace: > [] __rcu_pending+0x6e/0x1d9 > [] rcu_pending+0x36/0x6e > [] update_process_times+0x37/0x5b > [] tick_periodic+0x68/0x74 > [] tick_handle_periodic+0x21/0x66 > [] smp_apic_timer_interrupt+0x8a/0xa8 > [] apic_timer_interrupt+0x66/0x70 > [] ? acpi_safe_halt+0x2b/0x3e > [] ? acpi_idle_enter_c1+0xae/0x102 > [] ? cpuidle_idle_call+0x70/0xa2 > [] ? cpu_idle+0x7e/0x9c > [] ? start_secondary+0x157/0x15c > > Timer issue? Hmm, this is periodic mode so rather unlikely, but who knows. Does this happen with nohz and/or highres as well ? Thanks, tglx