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

RE: [Xen-devel] "Time went backwards" messages


  • To: "Don Fry" <brazilnut@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 5 Apr 2005 01:02:55 +0100
  • Delivery-date: Tue, 05 Apr 2005 00:02:53 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcU5b9Z1NLA+7kH8THGEGVlGXOh/awAAHOmg
  • Thread-topic: [Xen-devel] "Time went backwards" messages

> I have a high end IBM system with 4 HT CPUs, am running 
> xen-unstable with only Dom0 active, and I get lots of "Timer 
> ISR/n: Time went backwards" messages.  This is a short 
> segment from dmesg:

> The system has a Cyclone timer, and I am looking at using the 
> Cyclone timer to avoid the TSC drift, but while it is easy to 
> add to xen, all the cyclone support has been removed from linux.  

TSC drift? Are all the CPUs not running off the same bus clock on this
system?

It sounds like Xen just really isn't happy on this platform. If you look
at the Xen boot messages ('xm dmesg') does it look like it's identified
the CPU frequecies and local APIC (bus) clock correctly?

ian

> I have some prototype cyclone code added to xen, but have not 
> done anything to Linux yet.
> 
> --
> Don Fry
> brazilnut@xxxxxxxxxx
> 
> _______________________________________________
> 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®.