From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Runaway real/sys time in newer paravirt domUs? Date: Fri, 09 Jul 2010 09:46:05 +0100 Message-ID: <4C36FDED020000780000A6AA@vpn.id2.novell.com> References: <4C337E5D.7040407@goop.org> <053B0147-FC71-4440-896E-1A37E6A4CEEA@linode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <053B0147-FC71-4440-896E-1A37E6A4CEEA@linode.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jed Smith Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> On 08.07.10 at 18:38, Jed Smith wrote: > On Jul 6, 2010, at 3:05 PM, Jeremy Fitzhardinge wrote: >=20 >> I think this is the same problem as >> https://bugzilla.kernel.org/show_bug.cgi?id=3D16314=20 >=20 > If it is, it goes further back than 2.6.31 as that bug report suggests. = I=20 > was > able to reproduce it once in v2.6.30 as tagged, and am still laboring = to=20 > find > an A-B point to bisect. Failure rate is significantly lower in 2.6.30, = but > it did happen once. >=20 > So far, Ubuntu linux-image-ec2 (2.6.32-30{5,7}-ec2), our 2.6.32.12, = vanilla > 2.6.31, and vanilla 2.6.30 have demonstrated this issue in my testing > environment. All x86_64. I am unable to reproduce on i386 to this = point. Is this perhaps also dependent on the CPU make/model? Jan