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: Ian Marlier <ian.marlier@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 29 Oct 2007 14:47:01 -0400
Delivery-date: Mon, 29 Oct 2007 11:47:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200710280105.46032.jim_burn@xxxxxxxxxxxxx>
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
Thread-index: AcgaXBdIVbFZboZPEdyHJAAKlbpoWg==
Thread-topic: [Xen-users] Time went backwards / Stability issues
User-agent: Microsoft-Entourage/

On 10/28/07 1:05 AM, "jim burns" <jim_burn@xxxxxxxxxxxxx> wrote:

> On Sat October 27 2007 8:17:56 am Bart Verwilst wrote:
>> I've had the same troubles with the Ubuntu 2.6.22-14-xen kernel.
> Not just 2.6.22. Happens on fedora's 2.6.20 also. Everytime I close or open my
> laptop lid, the error gets triggered, so it must be acpi related. Haven't
> seen it in my test PV domUs, just dom0, but the only thing I keep running for
> any length of time is HVM.

Thanks to both Jim and Bart for their reports on this.

I found an older thread about this -- Bart's from earlier this month -- and
tried the jiffies clocksource suggestion there.

After changing the clocksource in _only_ dom0, the burn-in tests (that were
causing an error within minutes previously) have run for 72 hours straight
without causing any errors.  I've had full CPU utilization for that entire
period without a single clocksource issue.

My questions:
1) Is there any potential harm in changing the clocksource?  That is, is it
somehow important that the xen clocksource be used?

2) Bart and Jim, you guys have both seen this before; do either of you know
if there's a bug filed for this?  I searched the xensource bugzilla, but
wasn't able to find one -- but I find bugzilla very difficult to search.

- Ian

Xen-users mailing list