[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.


  • To: <joy@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: <Philippe.Simonet@xxxxxxxxxxxx>
  • Date: Thu, 5 Jan 2012 09:39:37 +0000
  • Accept-language: en-US, de-CH
  • Delivery-date: Thu, 05 Jan 2012 09:40:42 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AQHMywXO5+ao08/jK0mCGjzA8OSDsJX9g0nQ
  • Thread-topic: [Xen-devel] (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.

Hi

I have the same problem with 4 machines (hp dl385, AMD), the problem appears 
one time per machine and per month ...
No chance to re-produce it faster. On some other machine with another AMD 
processor, I never had this problem. Olivier Hanesse
reported the problem on some Intel CPU and not on other processor.

I'm using debian squeeze, with 

xen-hypervisor-4.0-amd64                4.0.1-4
linux-image-2.6.32-5-xen-amd64          2.6.32-38 (dom0)

that last changes that I have done is to add cpuidle=0 to hypervisor command 
line. stable since 3-4 weeks (...)

I have e test system that runs 20 paravirt. domus, with wheezy, with same 
problematic HW, with
xen-hypervisor-4.1-amd64                4.1.2-2
linux-image-3.1.0-1-amd64               3.1.6-1 (dom0)
and this system never had the TSC jump problem. but test system are test system 
....

I would be happy if you could reproduce the problem faster a me, so testing new 
xen / dom0 version could be
easier ...

thanks and regards

Philippe




> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Josip Rodin
> Sent: Wednesday, January 04, 2012 6:24 PM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] (XEN) Platform timer appears to have unexpectedly
> wrapped 10 or more times.
> 
> Hi,
> 
> Sometimes, seemingly randomly, long-running Xen domains, using
> clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often
> with the dom0 complaining about clocksource tsc. The number changes if the
> hypervisor is explicitly told to use clocksource=pit, but it still happens. It
> doesn't seem to be particularly hardware-specific.
> 
> See also http://bugs.debian.org/599161
> 
> I see from the archives that others have reported this problem here in
> February last year, but I couldn't find a resolution. Can anyone help?
> 
> (Please Cc: responses, I'm not subscribed.)
> 
> --
>      2. That which causes joy or happiness.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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