All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Chris Edwards <cedwards.linux@cedwards.geek.nz>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@amd64.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	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: Tue, 6 Dec 2011 12:17:03 +0100	[thread overview]
Message-ID: <20111206111703.GB17926@aftab> (raw)
In-Reply-To: <4EDD8314.3060904@cedwards.geek.nz>

On Tue, Dec 06, 2011 at 03:51:00PM +1300, Chris Edwards wrote:
> On 06/12/11 10:02, Thomas Gleixner wrote:
> >On Mon, 5 Dec 2011, Borislav Petkov wrote:
> >>On Mon, Dec 05, 2011 at 05:56:01PM +0100, Thomas Gleixner wrote:
> >>
> >>>You could try the following patch. Be aware that it might not work at
> >>>all, but I don't expect that you need a fire extinguisher :)
> 
> No smoke or flames noted. :)  And that appears to have solved the
> problem.  Firewire audio works, and even after running NetPIPE a
> couple of times over that Ethernet interface, there's only a handful
> of interrupts on the Firewire IRQ (as seems to be normal):

Oh ok, good.

I started poking at hw people for comments, let's see what happens. Please let
us know should there be other issues.

@tglx: You could give me a couple of days to confirm the workaround but
this is old stuff so don't hold your breath for too long :).

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2011-12-06 11:17 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
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 [this message]
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=20111206111703.GB17926@aftab \
    --to=bp@amd64.org \
    --cc=cedwards.linux@cedwards.geek.nz \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.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.