@@ -1664,6 +1664,15 @@ void set_pcie_hotplug_bridge(struct pci_dev *pdev)
pcie_capability_read_dword(pdev, PCI_EXP_SLTCAP, ®32);
if (reg32 & PCI_EXP_SLTCAP_HPC)
pdev->is_hotplug_bridge = 1;
+
+ /*
+ * When MSI is disabled, root port will use legacy INTX, and likely
+ * share INTX interrupt line with other devices like NIC/NVME. There
+ * was real world issue that the CCIE IRQ is asserted afer boot, but
+ * will not be handled well and cause IRQ storm. So disable it early.
+ */
+ if (!pci_msi_enabled())
+ pcie_disable_hp_interrupts_early(pdev);
}
static void set_pcie_thunderbolt(struct pci_dev *dev)
There was an irq storm bug when testing "pci=nomsi" case, and the root cause is: 'nomsi' will disable MSI and let devices and root ports use legacy INTX interrupt, and likely make several devices/ports share one interrupt. In the failure case, BIOS doesn't disable the pcie hotplug interrupts, and actually asserts the command-complete interrupt. So the timeline is: 1. pciehp's CCIE/HPIE enabled and command-complete interrupts asserted 2. the interrupt is shared by pcie root port and nvme/nic device 3. nvme/nic driver's probe function enables the interrupt line 4. pciehp driver is loaded later or not loaded And the "nobody cared irq storm" happens between 3 and 4. This is not an issue for normal MSI case, as each interrupt is controlled by its own driver. When the driver is not loaded, the interrupt won't get fired to kernel even if it is physically asserted. So disable the pcie hotplug CCIE/HPIE interrupt in early boot phase when MSI is not enabled. Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com> --- Changlog: Since v1: * Modify the commit log drivers/pci/probe.c | 9 +++++++++ 1 file changed, 9 insertions(+)