WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Timer ISR/0: Timer went backwards error...

To: Sandesh <sandesh.ahiremath@xxxxxxxxx>, "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] Timer ISR/0: Timer went backwards error...
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 03 Jul 2008 23:56:05 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 03 Jul 2008 15:56:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1215103390.4319.10.camel@ec4t16cg-1518809>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjdX/kLN4yiqklTEd2WvQAWy6hiGQ==
Thread-topic: [Xen-devel] Timer ISR/0: Timer went backwards error...
User-agent: Microsoft-Entourage/11.4.0.080122
On 3/7/08 17:43, "Sandesh" <sandesh.ahiremath@xxxxxxxxx> wrote:

> To be more specific about the problem, it happens only when i try to
> return from the hypervisor kdb. But since many others have/had the same
> problem without the use of hypervisor kdb, i dont think its due to the
> kdb. I had never got this error before, so suerly kdb must be triggering
> something here.

Quite a relevant bit of information I'd say. It's certainly related, since
time structures in Xen will not be updated and kept synchronised while kdb
has the system locked down. Indeed the time deltas you see are huge, so the
timeout in kdb has sent time handling haywire.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel