|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-devel
RE: [Xen-devel] Instability with Xen, interrupt routing frozen,	HPET bro 
| To: | "'Wei, Gang'" <gang.wei@xxxxxxxxx> |  
| Subject: | RE: [Xen-devel] Instability with Xen, interrupt routing frozen,	HPET broadcast |  
| From: | "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> |  
| Date: | Thu, 5 May 2011 09:53:26 -0500 |  
| Accept-language: | en-US |  
| Acceptlanguage: | en-US |  
| Cc: | "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Zhang,	Xiantao" <xiantao.zhang@xxxxxxxxx> |  
| Delivery-date: | Thu, 05 May 2011 07:55:29 -0700 |  
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |  
| In-reply-to: | <F26D193E20BBDC42A43B611D1BDEDE712CA1CAAE66@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |  
| 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: | <C872CBF75AC4BE4093DF425DEA49BA0809C63E5191@xxxxxxxxxxxxxxxxxxx>	<F26D193E20BBDC42A43B611D1BDEDE712CA1CAAE66@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |  
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |  
| Thread-index: | AcwKqwvW3Ga87kRkRM2m+5EkjC6gqQAQQVtAABH7hNA= |  
| Thread-topic: | [Xen-devel] Instability with Xen, interrupt routing frozen,	HPET broadcast |  
| > > I'm seeing similar issues.  If I disable C-states as Jimmy suggests
> > above, the problem goes away.  If I set the clocksource to 
> > pit, the problem goes away. It may go away also if I set the clocksource to 
> > pmtimer/acpi, or if I remove HPET from the list of available platform 
> > timers.
> > 
> We could not reproduce it, so no specific fix for it by far. 
> Have you tried the latest upstream?
So far, I haven't tried to reproduce with the latest upstream.
I will do that today if I can.
 
> When you mentioned clocksource, do you mean clocksource in 
> dom0 or in xen? I do think hpet broadcast code have nothing 
> to do with clocksource choice.
 
xen clocksource parameter.
--Mark Langsdorf
Operating System Research Center
AMD
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 | 
 |  | 
  
    |  |  |