This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] spurious interrupts

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] spurious interrupts
From: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Date: Wed, 12 Apr 2006 13:48:47 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 12 Apr 2006 10:49:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <443D1E9C.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <443D1E9C.76E4.0078.0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Wed, 2006-04-12 at 15:37 +0200, Jan Beulich wrote:

> While I haven't heard anything whether others were able to reproduce
> this, I was now able to nail this down to a simple operation: On the
> system I'm testing with I was able to identify that the handling of
> the interrupt from the SCSI controller triggers a simultaneous
> interrupt from one of the USB controllers

I've been seeing spurious irq16 on a USB port with no devices attached
for Xen for some time now, resulting in

        irq 16: nobody cared
on boot and 

         Disabling IRQ #16
ten minutes later once it reaches 100,000 unhandled interrupts.  With
today's build, including Keir's latest APIC changes, not only is serial
console input fixed (thanks Keir!), but the spurious IRQ also seems to
be solved.  (At least, at the time of writing that box is showing only
at 15,000 interrupts on irq16 after an hour instead of 100,000 after 10
minutes --- so I should know in another 5 hours whether or not it
actually still gets disabled at 100,000.)


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>