From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Soft lockup/Time went backwards in latest unstable Date: Mon, 26 Feb 2007 13:22:26 +0000 Message-ID: References: <82401315-95C2-4998-BB33-BE88A2AAB57F@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <82401315-95C2-4998-BB33-BE88A2AAB57F@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Derek Murray Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 26/2/07 12:39, "Derek Murray" wrote: > 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? Unfortunately not. There were big changes to Linux's time handling between 2.6.16 and 2.6.18 so bugs may hav ebeen introduced while porting out own timer code. It might be worth diffing the file time-xen.c from working and non-working Linux kernels. It's weird that the failure mode is bad on the T60p yet noone else has reported this bug, nor has our testing reproduced it. :-( -- Keir