From mboxrd@z Thu Jan 1 00:00:00 1970 From: "James Harper" Subject: RE: hang on restore in 3.3.1 Date: Wed, 11 Feb 2009 20:49:43 +1100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > On 11/02/2009 08:45, "James Harper" wrote: >=20 > > Now I'm seeing the same thing but on vector 0x93 instead. There is > > nothing on that vector. It appears that when xen is restoring my domain, > > an interrupt line is getting 'stuck' somehow, as the hang occurs as soon > > as I enable interrupts after doing the restore... any suggestions? >=20 > Not for a line that isn't connected up. Usually this is due to bad restore > of the evtchn callback irq, or bad restore of irqs from qemu. With 3.3 you > could of course try reverting to the in-tree qemu = (CONFIG_QEMU=3Dioemu) and > see if that makes the problem go away. I actually turn off the evtchn callback IRQ by setting it to 0. Even when I don't do this though the problem still occurs. When I analyse the IRR in windows, before enabling interrupts again, I can definitely see that the bit for vector 0x93 is set. Time to go digging... any suggestions for places to look? Thanks James