linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Edwards <cedwards.linux@cedwards.geek.nz>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: IRQ "nobody cared...Disabling" errors on linux-3.0.10-rt27 on SMP AMD64 system
Date: Mon, 5 Dec 2011 17:56:01 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1112051740510.2735@ionos> (raw)
In-Reply-To: <4EDCC978.3060401@cedwards.geek.nz>

On Tue, 6 Dec 2011, Chris Edwards wrote:

> On 05/12/11 02:32, Thomas Gleixner wrote:
> > On Sun, 4 Dec 2011, Chris Edwards wrote:
> > > On 04/12/11 05:29, Thomas Gleixner wrote:
> > > > Ok, that tells us something. So there is something unhappy in your
> > > > system about the way how the threaded irq handling works. Can you
> > > > please provide the output of lspci -vvv and a full boot log (any
> > > > 3.0/3.2 kernel you have handy)?
> > > Attached. :)
> > Could you disable the e1000 for a test? Just boot up and bring the
> > interface down.
> > 
> > Does that change the situation?
> 
> Yes - I tested with 3.2.0-rc4-rt5 (and it actually is an RT kernel this time -
> see below!) and with the Ethernet interface down, it seems to be working
> properly.  Even Pure Data didn't cause any crackling or stuttering (other than
> when starting up).
> 
> [    0.000000] Linux version 3.2.0-rc4-rt5 (root@babelfish) (gcc version 4.4.3
> (Ubuntu 4.4.3-4ubuntu5) ) #1 SMP PREEMPT RT Tue Dec 6 01:22:11 NZDT 2011
> [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.2.0-rc4-rt5
> root=UUID=ca21e0bf-b7f8-45c3-8fc9-066c4dd6052e ro quiet splash
> 
> What next?  Should I try moving the Ethernet card to other slots and see if
> anything changes?

That card hangs on the AMD bridge and that bridge has nasty interrupt
related erratas. Your "feature" is undocumented so far. It looks like
it sends interrupts which are masked, but pending over and over to a
different interrupt line :( We've seen this before. It's a legacy mode
feature, but your chip is excluded from the fixup.

Boris, any idea ?

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 :)

Thanks,

	tglx
---
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -1791,8 +1791,7 @@ static void quirk_disable_amd_813x_boot_interrupt(struct pci_dev *dev)
 
 	if (noioapicquirk)
 		return;
-	if ((dev->revision == AMD_813X_REV_B1) ||
-	    (dev->revision == AMD_813X_REV_B2))
+	if (dev->revision == AMD_813X_REV_B2)
 		return;
 
 	pci_read_config_dword(dev, AMD_813X_MISC, &pci_config_dword);


  reply	other threads:[~2011-12-05 16:56 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 [this message]
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=alpine.LFD.2.02.1112051740510.2735@ionos \
    --to=tglx@linutronix.de \
    --cc=borislav.petkov@amd.com \
    --cc=cedwards.linux@cedwards.geek.nz \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.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).