From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755588Ab0CQTWp (ORCPT ); Wed, 17 Mar 2010 15:22:45 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:47087 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755070Ab0CQTWn (ORCPT ); Wed, 17 Mar 2010 15:22:43 -0400 Date: Wed, 17 Mar 2010 12:22:41 -0700 From: "Paul E. McKenney" To: Ingo Molnar Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org, tglx@linutronix.de, linux-tip-commits@vger.kernel.org Subject: Re: [tip:core/rcu] rcu: Fix holdoff for accelerated GPs for last non-dynticked CPU Message-ID: <20100317192241.GB6806@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1267311188-16603-1-git-send-email-paulmck@linux.vnet.ibm.com> <20100316110036.GA4554@elte.hu> <20100316110323.GA31038@elte.hu> <20100317175311.GA5187@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100317175311.GA5187@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 Wed, Mar 17, 2010 at 06:53:11PM +0100, Ingo Molnar wrote: > > * Ingo Molnar wrote: > > > incidentally i have a RCU badness crash log from another box: > > > > [ 4.573332] initcall ipmi_init_msghandler_mod+0x0/0xd returned 0 after 0 usecs > > [ 4.573332] calling init_ipmi_si+0x0/0x435 @ 1 > > [ 4.573332] IPMI System Interface driver. > > [ 4.573340] [] no_context+0x1fc/0x20b > > [ 4.576672] [] ? ftrace_call+0x5/0x2b > > [ 4.580021] [] __bad_area_nosemaphore+0x18c/0x1af > > [ 4.583338] [] ? ftrace_call+0x5/0x2b > > [ 4.586672] [] bad_area_nosemaphore+0x13/0x15 > > [ 4.590005] [] do_page_fault+0x138/0x284 > > [ 4.593354] [] page_fault+0x1f/0x30 > > I spent a few hours yesterday and today trying to track this down, but failed > to bisect it. The crash is sporadic on many configs - which confused my > bisection attempts. Sometimes it crashes only after 10 reboots. Was able to > crash v2.6.30 as well, so it's an older bug. v2.6.29 was not testable on that > box due to network driver problems so i stopped there. OK, I give up... What did you change about your testing? ;-) Thanx, Paul