Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753863Ab0FNNeU (ORCPT ); Mon, 14 Jun 2010 09:34:20 -0400 Received: from www.tglx.de ([62.245.132.106]:56854 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753546Ab0FNNeS (ORCPT ); Mon, 14 Jun 2010 09:34:18 -0400 Date: Mon, 14 Jun 2010 15:33:54 +0200 (CEST) From: Thomas Gleixner To: "Darcy L. Watkins" cc: will_schmidt@vnet.ibm.com, LKML , rt-users , John Stultz , Nick Piggin Subject: Re: [ANNOUNCE] 2.6.33.5-rt23 In-Reply-To: <1276185942.31967.3.camel@localhost.localdomain> Message-ID: References: <1276119074.15867.311.camel@lexx> <1276185406.15867.390.camel@lexx> <1276185942.31967.3.camel@localhost.localdomain> 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 Content-Length: 2010 Lines: 55 On Thu, 10 Jun 2010, Darcy L. Watkins wrote: > > > On Thu, 2010-06-10 at 08:56 -0700, Will Schmidt wrote: > > On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > > > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > > > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > > > "sleeping function called from invalid context..." BUGs. The > > first was > > > > during system boot, second during a 'make'. > > > > > > > > relevant code paths don't seem to have changed between -rt22 and > > -rt23, > > > > so I think still valid.. :-) > > > > > > > > This is on a POWER7 system, which may have opened up some timing > > > > windows, wrt previous runs on POWER6 systems. > > > > > > > > > > > > BUG: sleeping function called from invalid context at > > > > kernel/rtmutex.c:684 > > > > > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node > > +0xdc/0x2b8 > > > > > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > > > it came back somehow. Can you disable that, or does you machine > > depend > > > on it ? > > > > I'm not sure whether it is required by the architecture. I do see > > that > > SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I > > don't see an equivalent 'disable' in arch/powerpc/Kconfig. > > > > I see it as "y" in my .config for a powerpc 405 build. This appears to > run on my system (although I haven't loaded up the rt23 build on the > target yet - last one loaded up was rt22). > > What should I expect to see different if SPARSE_IRQ is turned off? The difference is that you can trigger "scheduling while atomic". The warning Will has seen depends on debug options. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/