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


[Xen-users] clocksource/0: Time went backwards

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] clocksource/0: Time went backwards
From: Lists <lists@xxxxxxxxxxx>
Date: Wed, 10 Oct 2007 00:08:09 +0200 (CEST)
Delivery-date: Tue, 09 Oct 2007 15:09:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Dear fellow Xen'ers!

I'm having a problem with my new Xen-enabled colocation server.. I hope ( at 
least ;) ) one of you guys know how to fix this problem..

For a certain amount of time ( 1-2 days ) the domU runs fine.. until the 
console starts spitting out messages like these:

[80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 
shadow=80182004054805 offset=400471
[80182.004507] clocksource/0: Time went backwards: delta=-6917292717540005396 
shadow=80182004054805 offset=450712
[80182.004762] clocksource/0: Time went backwards: delta=-6917292717539750360 
shadow=80182004054805 offset=705812
[80182.004842] clocksource/0: Time went backwards: delta=-6917292717539670405 
shadow=80182004054805 offset=785744
[80182.004918] clocksource/0: Time went backwards: delta=-6917292717539594298 
shadow=80182004054805 offset=861851

The only action left is an xm shutdown, after which an xm create boots up the 
machine fine for the next couple of days..

I'm running Ubuntu 7.10, with the stock xen kernel ( 2.6.22-13-xen ).

An ubuntu bug has already been reported and appended to by multiple persons 


Anyone have any ideas/patches/hints/.../anything that can help?

Thanks a lot guys!

Kind regards,

Bart Verwilst

Xen-users mailing list