[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M)


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Bruce Edge <bruce.edge@xxxxxxxxx>
  • Date: Fri, 20 Aug 2010 16:25:06 -0700
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
  • Delivery-date: Fri, 20 Aug 2010 16:26:00 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Uwi7BhtvqeEGlk/jixu/yY7VPfiEGDzyAf3HmyIZcz/hoCgkN6fMijCDhERqWa4QUQ 2Ubk8RCI9g3ow2UjK2kMoi1LlqbCpr3CgUPHfw1bKj9gqi6kx/uBtzibR4SjlbTtaqtC +ThTWJLOzyRPTUVeM/8FCpgZAHDOOkAVPJLZU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Thu, Aug 19, 2010 at 8:48 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
On 19/08/2010 14:42, "Bruce Edge" <bruce.edge@xxxxxxxxx> wrote:

> Is there any more information that I can provide that would be helpful in
> diagnosing the direct cause and the appropriate fix?
> Possibly adding instrumentation or trace code to detect the trigger
> conditions?
> This is very repeatable on our target systems after a few hours of load.

You can try the attached Xen patch which should clear out the in-flight
interrupt after a short timeout. It might kick things back into action, and
is probably a fix we should have in the tree anyhow.

 -- Keir


Thanks Kier, this patch definitely works.

It's running on 2 machines under load, well past where they consistently have failed in the past.

-Bruce

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.