From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: Oops during Init IRQ Date: Wed, 20 Jun 2012 08:40:34 +0200 (CEST) Message-ID: References: <4FDF32DD.3010800@c-s.fr> <4FE03CCE.8000603@c-s.fr> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: linux-rt-users , Steven Rostedt To: leroy christophe Return-path: Received: from www.linutronix.de ([62.245.132.108]:51625 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752664Ab2FTGkg (ORCPT ); Wed, 20 Jun 2012 02:40:36 -0400 In-Reply-To: <4FE03CCE.8000603@c-s.fr> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Tue, 19 Jun 2012, leroy christophe wrote: > Hello, > > Yes it does fix the issue. > Thanks a lot. > > Shall I do anything to ask for this change to be included either in the kernel > or in the rt patch ? We'll take care. Thanks. Steven, can you please pick that up for stable-rt ? It's in my queue, but I won't be able to release before the weekend. Thanks, tglx > > > > > > Index: linux-3.4/arch/powerpc/platforms/8xx/m8xx_setup.c > > =================================================================== > > --- linux-3.4.orig/arch/powerpc/platforms/8xx/m8xx_setup.c > > +++ linux-3.4/arch/powerpc/platforms/8xx/m8xx_setup.c > > @@ -43,6 +43,7 @@ static irqreturn_t timebase_interrupt(in > > static struct irqaction tbint_irqaction = { > > .handler = timebase_interrupt, > > + .flags = IRQF_NO_THREAD, > > .name = "tbint", > > }; > > Index: linux-3.4/arch/powerpc/sysdev/cpm1.c > > =================================================================== > > --- linux-3.4.orig/arch/powerpc/sysdev/cpm1.c > > +++ linux-3.4/arch/powerpc/sysdev/cpm1.c > > @@ -120,6 +120,7 @@ static irqreturn_t cpm_error_interrupt(i > > static struct irqaction cpm_error_irqaction = { > > .handler = cpm_error_interrupt, > > + .flags = IRQF_NO_THREAD, > > .name = "error", > > }; > > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >