From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Edwards <cedwards.linux@cedwards.geek.nz>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: IRQ "nobody cared...Disabling" errors on linux-3.0.10-rt27 on SMP AMD64 system
Date: Wed, 23 Nov 2011 08:52:43 -0500 [thread overview]
Message-ID: <1322056363.20742.45.camel@frodo> (raw)
In-Reply-To: <4ECCE979.5080109@cedwards.geek.nz>
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?
>
> System:
> Dual Opteron 244 processors on an Iwill DK8N (AMD 8131 and nForce3 250Gb)
> Ubuntu 10.04.3 LTS
>
> I did try the "irqpoll" kernel command-line option as suggested in the
> error messages, but the kernel messages say that it's not supported in -rt.
Right. There's an issue on some chipsets that running interrupts as
threads causes the chipset to go into legacy mode, and interrupts coming
in on one apic line, appear on another line. There is a work around for
it (I believe), and we black list these chipsets, but as with all black
lists, we only list those that we know about. Yours may be a new one.
>
> Needless to say, the Firewire audio is a no-go.
>
> I'm also having trouble getting dual-head X to work, but that's another
> issue, most likely. I'm also wondering if I can get the HPET timer
> enabled: AFAICT (from looking at other BIOSes) the nForce3 has one, but
> this system's ACPI tables don't advertise it.
Keep us posted. Thanks!
-- Steve
next prev parent reply other threads:[~2011-11-23 13:52 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 [this message]
2011-11-23 23:12 ` Chris Edwards
2011-11-29 2:25 ` Chris Edwards
2011-11-30 22:10 ` Steven Rostedt
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=1322056363.20742.45.camel@frodo \
--to=rostedt@goodmis.org \
--cc=cedwards.linux@cedwards.geek.nz \
--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).