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 -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
