From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: Instability with Xen, interrupt routing frozen, HPET
	broadcast
Date: Sun, 09 Jan 2011 20:10:52 +0100
Message-ID: <4D2A083C.1070504@hfp.de>
References: <4C88A6F3.9020207@hfp.de> <20101231143138.GC2754@reaktio.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20101231143138.GC2754@reaktio.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, JBeulich@novell.com
List-Id: xen-devel@lists.xenproject.org

On 31.12.2010 15:31, Pasi K=E4rkk=E4inen 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 machin=
e
>> 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=20
of it.

Regards Andreas