[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: Bruce Edge <bruce.edge@xxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 19 Aug 2010 16:48:45 +0100
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
  • Delivery-date: Thu, 19 Aug 2010 08:49:38 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acs/pGKtqPPZelWXRf6LoA7QG/sA0gAEZ63i
  • Thread-topic: [Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M)

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

Attachment: 00-irq-eoi-timer
Description: Binary data

_______________________________________________
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®.