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] Soft lockup/Time went backwards in latest unstable

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Soft lockup/Time went backwards in latest unstable
From: Derek Murray <Derek.Murray@xxxxxxxxxxxx>
Date: Mon, 26 Feb 2007 12:39:00 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 26 Feb 2007 04:39:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C205245B.2928%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C205245B.2928%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 23 Feb 2007, at 23:08, Keir Fraser wrote:

You should be able to run a 3.0.3 dom0 on 3.0.4 Xen and vice versa. By
trying both combinations you should be able to work out whether it is the
Xen upgrade or the Linux upgrade which introduces the problem.

It appears I was being hasty in blaming 3.0.4 for introducing the bug. I tested the following configurations:

Xen 3.0.3_0: works with 3.0.3 kernel (2.6.16.29-xen) and 3.0.4 kernel (2.6.16.33-xen). Fails with -unstable kernel (2.6.18). Xen 3.0.4_1: works with 3.0.3 and 3.0.4 kernels. Fails with -unstable kernel. Xen unstable: works with 3.0.3 and 3.0.4 kernels. Fails with - unstable kernel.

So, 3.0.3 and 3.0.4 work as distributed, but the latest -unstable is broken.

The reason I attributed the blame to 3.0.4 was because I had seen the same bug in -unstable during the 3.0.3-3.0.4 interregnum; however, this bug seems to have been fixed for the 3.0.4 release, and re- emerged since with the transition to 2.6.18.

Is there a pattern for how these bugs have been fixed in the past, so that I could go about trying to make a patch?

Regards,

Derek Murray.




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