Date: Fri, 15 May 2015 14:42:25 +0000 From: "Eggert, Lars" <lars@netapp.com> To: =?utf-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Message-ID: <91758942-3683-42E5-9B39-66775E48D4DF@netapp.com> In-Reply-To: <55560414.1040002@citrix.com> References: <EAB58E00-BA0A-45FB-A709-01359219C106@netapp.com> <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <5553651D.3000400@citrix.com> <FFAA0565-3513-4097-A356-8BED9DB61307@netapp.com> <5555DFBC.9030306@citrix.com> <683335F9-E04E-4F8C-B1EF-0047E63E00AD@netapp.com> <5555FF4A.8010702@citrix.com> <126FDC37-2822-45DB-9AA6-3C9A03D89959@netapp.com> <55560414.1040002@citrix.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2015-5-15, at 16:35, Roger Pau Monné <roger.pau@citrix.com> wrote: > > Yes, but I've realized that isci for example passes an uint32_t instead > of an int, so it might be best to set it to 0. Here is what I see now: 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: isci->num_interrupts: 2 max_msix_messages: 2 isci: 1:000089 ISCI bus_alloc_resource failed The storm is still there. Will now set hw.isci.force_legacy_interrupts=1 and check if the device then works correctly. Lars [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlVWBc8ACgkQIWcjmsUTWRqNOQCgje1hu/4v/52KA071ab2Sd9Gt 7REAnjAtOIO2lZmpUGCbq/vBKH5X0Coi =7N1K -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91758942-3683-42E5-9B39-66775E48D4DF>
