From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Edwards <cedwards@ripples.dyndns.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: IRQ "nobody cared...Disabling" errors on linux-3.0.10-rt27 on SMP AMD64 system
Date: Wed, 30 Nov 2011 17:10:17 -0500 [thread overview]
Message-ID: <1322691017.24563.9.camel@frodo> (raw)
In-Reply-To: <4ECD7DCC.3000505@ripples.dyndns.org>
On Thu, 2011-11-24 at 12:12 +1300, Chris Edwards wrote:
> On 24/11/11 02:52, Steven Rostedt wrote:
> > On Thu, 2011-11-24 at 01:39 +1300, Chris Edwards wrote:
> >> Hi all,
> >>
> >> Problem:
> >> IRQ-related "nobody cared" kernel call traces not long after bootup on
> >> Linux 3.0.10-rt27. I thought I'd try a -rt kernel to see if it would
> >> resolve the audio drop-outs on my new Firewire audio interface.
> > I wonder if this is another bad irq chipset. Does it go away if you boot
> > with noapic in the kernel command line?
> >
>
> Thanks for the quick reply, Steven. Booting with "noapic" does seem to
> avoid the problem with IRQs 17 and 18, and the Firewire audio now works,
> but the "nobody cared" error now appears for IRQ 7:
A couple of things:
Could you also try mainline, with "threadirqs" on the command line and
see if it gives you the same issue. It should also tell you if it is a
chipset problem or not. Try v3.0, and then v3.2.
Could you also apply the below patch to 3.0-rt. Thomas pointed me to the
following commits. The patch below is a back port of them.
commit 52553ddff
commit c75d720f
Oh, and remove the noapic from the command line when you do all of this.
Thanks,
-- Steve
diff --git a/kernel/irq/spurious.c b/kernel/irq/spurious.c
index e57f1b3..d09e0f5 100644
--- a/kernel/irq/spurious.c
+++ b/kernel/irq/spurious.c
@@ -84,7 +84,9 @@ static int try_one_irq(int irq, struct irq_desc *desc, bool force)
*/
action = desc->action;
if (!action || !(action->flags & IRQF_SHARED) ||
- (action->flags & __IRQF_TIMER) || !action->next)
+ (action->flags & __IRQF_TIMER) ||
+ (action->handler(irq, action->dev_id) == IRQ_HANDLED) ||
+ !action->next)
goto out;
/* Already running on another processor */
@@ -115,7 +117,7 @@ static int misrouted_irq(int irq)
struct irq_desc *desc;
int i, ok = 0;
- if (atomic_inc_return(&irq_poll_active) == 1)
+ if (atomic_inc_return(&irq_poll_active) != 1)
goto out;
irq_poll_cpu = smp_processor_id();
next prev parent reply other threads:[~2011-11-30 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 12:39 IRQ "nobody cared...Disabling" errors on linux-3.0.10-rt27 on SMP AMD64 system Chris Edwards
2011-11-23 13:52 ` Steven Rostedt
2011-11-23 23:12 ` Chris Edwards
2011-11-29 2:25 ` Chris Edwards
2011-11-30 22:10 ` Steven Rostedt [this message]
2011-12-03 9:41 ` Chris Edwards
2011-12-03 10:42 ` Chris Edwards
2011-12-03 16:29 ` Thomas Gleixner
[not found] ` <4EDAAEFD.9060209@ripples.dyndns.org>
2011-12-04 13:32 ` Thomas Gleixner
2011-12-05 13:39 ` Chris Edwards
2011-12-05 16:56 ` Thomas Gleixner
2011-12-05 18:14 ` Borislav Petkov
2011-12-05 21:02 ` Thomas Gleixner
2011-12-06 2:51 ` Chris Edwards
2011-12-06 11:17 ` Borislav Petkov
2011-12-07 0:32 ` Thomas Gleixner
2011-12-06 19:42 ` Borislav Petkov
2011-12-07 0:37 ` Thomas Gleixner
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=1322691017.24563.9.camel@frodo \
--to=rostedt@goodmis.org \
--cc=cedwards@ripples.dyndns.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.