Date: Wed, 13 May 2015 16:52:13 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: "Eggert, Lars" <lars@netapp.com> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Message-ID: <5553651D.3000400@citrix.com> In-Reply-To: <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> References: <EAB58E00-BA0A-45FB-A709-01359219C106@netapp.com> <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
El 13/05/15 a les 15.48, Eggert, Lars ha escrit:
> isci0: <Intel(R) C600 Series Chipset SAS Controller (SATA mode)> port 0x6000-0x60ff mem 0xde07c000-0xde07ffff,0xddc00000-0xddffffff irq 16 at device 0.0 on pci10
> isci0: attempting to allocate 2 MSI-X vectors (2 supported)
> isci: 1:000089 ISCI bus_alloc_resource failed
This device is sharing the same IRQ#16 with ehci0, and I have a feeling
it's not properly setting up it's interrupt sources. First, FreeBSD
Dom0 still doesn't support MSI-X (only MSI), but isci doesn't check the
errors returned by pci_alloc_msix. I have a patch for FreeBSD which
might solve it, however I don't have any similar box I can use to test
it, would you mind giving it a spin?
Thanks, Roger.
---
diff --git a/sys/x86/xen/xen_msi.c b/sys/x86/xen/xen_msi.c
index 0f678b1..181b956 100644
--- a/sys/x86/xen/xen_msi.c
+++ b/sys/x86/xen/xen_msi.c
@@ -114,6 +114,7 @@ int
xen_msix_alloc(device_t dev, int *irq)
{
+ *irq = -1;
return (ENXIO);
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5553651D.3000400>