From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Timer ISR/0: Timer went backwards error... Date: Thu, 03 Jul 2008 23:56:05 +0100 Message-ID: References: <1215103390.4319.10.camel@ec4t16cg-1518809> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1215103390.4319.10.camel@ec4t16cg-1518809> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sandesh , "dan.magenheimer@oracle.com" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 3/7/08 17:43, "Sandesh" 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