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


RE: [Xen-users] Time went backwards / Stability issues

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Time went backwards / Stability issues
From: "Marlier, Ian" <ian.marlier@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 29 Oct 2007 19:21:14 -0400
Delivery-date: Mon, 29 Oct 2007 16:22:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <603140762.1581193693578598.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx>
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>
References: <C34BA2E5.71B2D%ian.marlier@xxxxxxxxxxxxxxxxxxx> <603140762.1581193693578598.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acgac2NFlsGCpOpcTXWEYmD1grLbswADd5kw
Thread-topic: [Xen-users] Time went backwards / Stability issues

> -----Original Message-----
> From: Bart Verwilst [mailto:lists@xxxxxxxxxxx] 
> Sent: Monday, October 29, 2007 5:33 PM
> To: Marlier, Ian
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Time went backwards / Stability issues
> Hi Ian,
> Well, I've posted an Ubuntu report here 
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/
> +bug/146924 , with a reference to 
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=195 , 
> which seems pretty much the same bug..
> Kind regards,
> Bart Verwilst

I'm actually not sure that 195 is the same bug; though the error message
is the same, that bug was reported against the 2.0 codebase, and it's
not clear to me whether the Timer module that was referenced there is
still in use in the clocksource stuff.

In any case, I went ahead and filed a new bug specifically for the
clocksource issue.  It's here:

Xen-users mailing list