All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, Don Zickus <dzickus@redhat.com>,
	Don Dutile <ddutile@redhat.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Asit Mallick <asit.k.mallick@intel.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] irq: add quirk for broken interrupt remapping on 55XX chipsets
Date: Sat, 02 Mar 2013 11:21:29 -0500	[thread overview]
Message-ID: <51322709.6060702@redhat.com> (raw)
In-Reply-To: <1362158276-4901-1-git-send-email-nhorman@tuxdriver.com>

On 03/01/2013 12:17 PM, Neil Horman wrote:
> A few years back intel published a spec update:
> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
> 
> For the 5520 and 5500 chipsets which contained an errata (specificially errata
> 53), which noted that these chipsets can't properly do interrupt remapping, and
> as a result the recommend that interrupt remapping be disabled in bios.  While
> many vendors have a bios update to do exactly that, not all do, and of course
> not all users update their bios to a level that corrects the problem.  As a
> result, occasionally interrupts can arrive at a cpu even after affinity for that
> interrupt has be moved, leading to lost or spurrious interrupts (usually
> characterized by the message:
> kernel: do_IRQ: 7.71 No irq handler for vector (irq -1)
> 
> There have been several incidents recently of people seeing this error, and
> investigation has shown that they have system for which their BIOS level is such
> that this feature was not properly turned off.  As such, it would be good to
> give them a reminder that their systems are vulnurable to this problem.
> 
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> CC: Prarit Bhargava <prarit@redhat.com>
> CC: Don Zickus <dzickus@redhat.com>
> CC: Don Dutile <ddutile@redhat.com>
> CC: Bjorn Helgaas <bhelgaas@google.com>
> CC: Asit Mallick <asit.k.mallick@intel.com>
> CC: linux-pci@vger.kernel.org
> ---
>  drivers/iommu/intel_irq_remapping.c | 20 ++++++++++++++++++++
>  include/linux/pci_ids.h             |  2 ++
>  2 files changed, 22 insertions(+)
> 
> diff --git a/drivers/iommu/intel_irq_remapping.c b/drivers/iommu/intel_irq_remapping.c
> index f3b8f23..9bfb6c2 100644
> --- a/drivers/iommu/intel_irq_remapping.c
> +++ b/drivers/iommu/intel_irq_remapping.c
> @@ -1113,3 +1113,23 @@ struct irq_remap_ops intel_irq_remap_ops = {
>  	.msi_setup_irq		= intel_msi_setup_irq,
>  	.setup_hpet_msi		= intel_setup_hpet_msi,
>  };
> +
> +
> +static void intel_remapping_check(struct pci_dev *dev)
> +{
> +	u8 revision;
> +
> +	pci_read_config_byte(dev, PCI_REVISION_ID, &revision);
> +
> +	if ((revision == 0x13) && irq_remapping_enabled) {
> +		pr_warn("WARNING WARNING WARNING WARNING WARNING WARNING\n"
> +			"This system BIOS has enabled interrupt remapping\n"
> +			"on a chipset that contains an errata making that\n"
> +			"feature unstable.  Please reboot with nointremap\n"
> +			"added to the kernel command line and contact\n"
> +			"your BIOS vendor for an update");

Make this one line?  Might be too long but I believe the preferred policy is now
to keep the output on one line so that it is easy to find in the kernel source.

Also, IMO, remove the WARNING WARNING stuff.

You also should probably use HW_ERR here too.

P.

> +	}
> +}
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_5520_IOHUB, intel_remapping_check);
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_5500_IOHUB, intel_remapping_check);
> +
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 31717bd..54027a6 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2732,6 +2732,8 @@
>  #define PCI_DEVICE_ID_INTEL_LYNNFIELD_MC_CH2_RANK_REV2  0x2db2
>  #define PCI_DEVICE_ID_INTEL_LYNNFIELD_MC_CH2_TC_REV2    0x2db3
>  #define PCI_DEVICE_ID_INTEL_82855PM_HB	0x3340
> +#define PCI_DEVICE_ID_INTEL_5500_IOHUB	0x3403
> +#define PCI_DEVICE_ID_INTEL_5520_IOHUB	0x3406
>  #define PCI_DEVICE_ID_INTEL_IOAT_TBG4	0x3429
>  #define PCI_DEVICE_ID_INTEL_IOAT_TBG5	0x342a
>  #define PCI_DEVICE_ID_INTEL_IOAT_TBG6	0x342b


  parent reply	other threads:[~2013-03-02 16:21 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 17:17 [PATCH] irq: add quirk for broken interrupt remapping on 55XX chipsets Neil Horman
2013-03-01 18:20 ` Yinghai Lu
2013-03-01 19:29   ` Neil Horman
2013-03-02  2:28   ` Jiang Liu
2013-03-02 15:59 ` Andreas Mohr
2013-03-04 13:24   ` Don Dutile
2013-03-10  1:11     ` Prarit Bhargava
2013-03-02 16:21 ` Prarit Bhargava [this message]
2013-03-02 20:13   ` Neil Horman
2013-03-04 19:04 ` [PATCH v2] " Neil Horman
2013-03-09 20:49   ` Neil Horman
2013-03-09 22:20     ` Myron Stowe
2013-03-11  1:31       ` Don Dutile
2013-03-11 11:25       ` Neil Horman
2013-03-11 12:17         ` Prarit Bhargava
2013-04-03 23:53   ` Bjorn Helgaas
2013-04-04 11:17     ` Neil Horman
2013-04-04 14:27     ` David Woodhouse
2013-04-04 14:50       ` Neil Horman
2013-04-04 14:50         ` Neil Horman
2013-04-04 14:57         ` Bjorn Helgaas
2013-04-04 15:39           ` Neil Horman
2013-04-04 17:14             ` Bjorn Helgaas
2013-04-04 17:14               ` Bjorn Helgaas
2013-04-04 17:51               ` Neil Horman
2013-04-04 18:41                 ` Bjorn Helgaas
2013-04-04 18:41                   ` Bjorn Helgaas
2013-04-04 20:02                   ` Neil Horman
2013-04-04 13:54 ` [PATCH v3] " Neil Horman
2013-04-04 15:08 ` [PATCH v4] " Neil Horman
2013-04-04 16:16   ` Yinghai Lu
2013-04-04 17:27     ` Don Dutile
2013-04-04 17:40       ` Yinghai Lu
2013-04-04 20:04         ` Neil Horman
2013-04-04 20:33           ` Bjorn Helgaas
2013-04-04 21:11             ` Yinghai Lu
2013-04-05  0:24               ` Neil Horman
2013-04-05 19:25 ` [PATCH v5] " Neil Horman
2013-04-05 19:29   ` Neil Horman
2013-04-05 19:31 ` [PATCH v6] " Neil Horman
2013-04-05 23:37   ` Yinghai Lu
2013-04-06  1:55   ` Bjorn Helgaas
2013-04-08 15:29     ` Don Dutile
2013-04-08 17:17       ` Bjorn Helgaas
2013-04-08 17:42         ` Neil Horman
2013-04-09 10:08           ` Joerg Roedel
2013-04-15 11:18 ` [PATCH v7] " Neil Horman
2013-04-15 15:30   ` Bjorn Helgaas
2013-04-15 16:28     ` Neil Horman
2013-04-15 16:28 ` [PATCH v8] " Neil Horman
2013-04-15 22:41 ` [PATCH v9] " Neil Horman
2013-04-15 23:02   ` Yinghai Lu
2013-04-16  0:43     ` Neil Horman
2013-04-16  6:20   ` Arkadiusz Miskiewicz
2013-04-16 10:24   ` Joerg Roedel
2013-04-16 13:07     ` Neil Horman
2013-04-16 13:35     ` Neil Horman
2013-04-16 16:37       ` Joerg Roedel
2013-04-16 17:25         ` Neil Horman
2013-04-16 20:38 ` [PATCH v10] " Neil Horman
2013-04-16 22:08   ` Don Dutile
2013-04-18 15:02   ` Joerg Roedel
2013-04-18 17:00     ` Neil Horman

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=51322709.6060702@redhat.com \
    --to=prarit@redhat.com \
    --cc=asit.k.mallick@intel.com \
    --cc=bhelgaas@google.com \
    --cc=ddutile@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /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.