From: Thomas Gleixner <tglx@linutronix.de>
To: leroy christophe <christophe.leroy@c-s.fr>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Oops during Init IRQ
Date: Mon, 18 Jun 2012 19:53:17 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1206181949160.3086@ionos> (raw)
In-Reply-To: <4FDF32DD.3010800@c-s.fr>
On Mon, 18 Jun 2012, leroy christophe wrote:
> Hello,
>
> I'm trying to use the rt10 patch on a 3.4.2 kernel on a powerpc (MPC8xx)
> system, and I'm having the following Oops during Irq initialisation. This
> happens with CONFIG_PREEMPT_RT_FULL.
> It doesn't happen with CONFIG_PREEMPT__LL
>
> May someone help ?
Does the following uncompiled and untested patch fix it for you ?
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",
};
next prev parent reply other threads:[~2012-06-18 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 13:53 Oops during Init IRQ leroy christophe
2012-06-18 17:53 ` Thomas Gleixner [this message]
2012-06-19 8:48 ` leroy christophe
2012-06-20 6:40 ` Thomas Gleixner
2012-06-20 11:33 ` Steven Rostedt
2012-06-22 11:30 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1206181949160.3086@ionos \
--to=tglx@linutronix.de \
--cc=christophe.leroy@c-s.fr \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).