From owner-freebsd-xen@FreeBSD.ORG Fri May 15 12:00:07 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8781D379 for ; Fri, 15 May 2015 12:00:07 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3ACE710D0 for ; Fri, 15 May 2015 12:00:06 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,433,1427760000"; d="scan'208";a="265455712" Message-ID: <5555DFBC.9030306@citrix.com> Date: Fri, 15 May 2015 13:59:56 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Eggert, Lars" CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <5553651D.3000400@citrix.com> In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2015 12:00:07 -0000 El 15/05/15 a les 13.53, Eggert, Lars ha escrit: > On 2015-5-13, at 16:52, Roger Pau Monné wrote: >> 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? > > Unfortunately, the irq storm is still present with that patch applied. Can you provide the bootlog with the patch applied? Also, can you try if there's any difference when setting: hw.isci.force_legacy_interrupts=1 on /boot/loader.conf? Thanks, Roger.