From: Thomas Gleixner <tglx@linutronix.de>
To: Borislav Petkov <bp@amd64.org>
Cc: Chris Edwards <cedwards.linux@cedwards.geek.nz>,
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 22:02:27 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1112052200190.2735@ionos> (raw)
In-Reply-To: <20111205181450.GK7834@aftab>
On Mon, 5 Dec 2011, Borislav Petkov wrote:
> On Mon, Dec 05, 2011 at 05:56:01PM +0100, Thomas Gleixner wrote:
> > 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 ?
>
> Hmm, that's the old 8131 chipset, correct?
>
> > 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;
>
> Ok, according to my docs, this erratum you're addressing here is
> supposed to be fixed in revision B1 of the chipset but your test patch
> enables the quirk for B1 too.
>
> What is dev->revision on that board, 0x12?
Yep:
[ 0.716126] pci 0000:03:01.0: AMD8131 rev 12 detected; disabling PCI-X MMRBC
[ 0.716138] pci 0000:03:02.0: AMD8131 rev 12 detected; disabling PCI-X MMRBC
But that interrupt behaviour is exaclty the same which we saw with the
other pre rev 12 versions. So I just wanted Edward to try that quirk
and see whether it solves his issues.
Thanks,
tglx
next prev parent reply other threads:[~2011-12-05 21:02 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 [this message]
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.1112052200190.2735@ionos \
--to=tglx@linutronix.de \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--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).