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] Instability with Xen, interrupt routing frozen, HPET bro

To: Andreas Kinzler <ml-xen-devel@xxxxxx>
Subject: Re: [Xen-devel] Instability with Xen, interrupt routing frozen, HPET broadcast
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 9 Jan 2011 21:21:51 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, JBeulich@xxxxxxxxxx
Delivery-date: Sun, 09 Jan 2011 11:22:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D2A083C.1070504@xxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C88A6F3.9020207@xxxxxx> <20101231143138.GC2754@xxxxxxxxxxx> <4D2A083C.1070504@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sun, Jan 09, 2011 at 08:10:52PM +0100, Andreas Kinzler wrote:
> On 31.12.2010 15:31, Pasi Kärkkäinen wrote:
>> On Thu, Sep 09, 2010 at 11:20:51AM +0200, Andreas Kinzler wrote:
>>>   I am talking a while (via email) with Jan now to track the following
>>> problem and he suggested that I report the problem on xen-devel:
>>> I also applied a small patch which disables HPET broadcast. The machine
>>> is now running
>>> for 110 hours without a crash while normally it crashes within a few
>>> minutes. Is there
>>> something wrong (race, deadlock) with HPET broadcasts in relation to
>>> blocked interrupt
>>> reception (see above)?
>> Hello,
>> Was this issue resolved? Just wondering since many people
>> have reported it on xen-users list..
>> -- Pasi
> As to my knowledge: not at all. Somehow none of the developers took care  
> of it.

So you can still reproduce it with latest xen-4.0-testing.hg (Xen 4.0.2-rc1-pre)
and latest xen/stable-2.6.32.x pvops dom0 kernel ( ? 

-- Pasi

Xen-devel mailing list