From owner-freebsd-current@FreeBSD.ORG Fri Jul 16 06:34:41 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36FA81065672 for ; Fri, 16 Jul 2010 06:34:41 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B7F6D8FC0A for ; Fri, 16 Jul 2010 06:34:40 +0000 (UTC) Received: by fxm13 with SMTP id 13so936129fxm.13 for ; Thu, 15 Jul 2010 23:34:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EBu+sdS9wVg03SJ1CR1txDgs0iryvhRmFRl8do+gPkA=; b=Hq+Zp+7j0m8g2el7Yosg7Wp3m6jV8JDl/0RMfRRBTiOYJQj574u6dFuel6YXQWZFbV vSUiYfSgqXzNAqRs+1/EdkghuuBhSCAiBYa2WdkqQPIBgidvbRCi3VtMVkTqI5xxiBvu 0awrbcqc8v2m8P3Nt+0lHzqQheOOHwA7RnWBc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=GdEcXhW7s+d2GP6/X13DAO0thzsrnvdpNQV9aGeWmA/lI5Jcm0c5SjMa/uf/mgOTkR o2Dqvuoopqwo/3qy848HcXvYpUe1sqtPR1hSFd07HhL20o5qsW3oYwmST+a/TBkh8U9A wbPG+uTnc+bZVR+G0zc4m5Z/KQKmS4wDAQ+p8= Received: by 10.223.107.137 with SMTP id b9mr276006fap.17.1279262079599; Thu, 15 Jul 2010 23:34:39 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id a9sm633725faa.27.2010.07.15.23.34.38 (version=SSLv3 cipher=RC4-MD5); Thu, 15 Jul 2010 23:34:38 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C3FFD3F.7060909@FreeBSD.org> Date: Fri, 16 Jul 2010 09:33:35 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Rob Farmer , current References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Clock not moving in virtual machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2010 06:34:41 -0000 Rob Farmer wrote: > I have a VPS from rootbsd.net which is running current, though I don't > update it very often. I just built and installed a new world and > kernel and now the clock will not move from the time the system was > booted, ie: > # date > Thu Jul 15 16:15:58 PDT 2010 > > # date > Thu Jul 15 16:15:58 PDT 2010 > > I have an old kernel from May 27 which doesn't have this problem. I > noticed some clock related stuff changing in current in the last > couple of weeks and suspect that their VM setup doesn't play well with > these changes (their site says they use Xen, but several boot messages > refer to QEMU). Officially, I think they only support running 8.0 so I > thought I would ask here if anyone has any ideas before putting in a > support request. > > Here's a diff of the dmesgs - I can post full copies if needed but > didn't want to start with a ridicously long message: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 0 package(s) x 16 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 0 Probably not related, but funny. :) So you have two CPUs? > @@ -81,7 +81,10 @@ > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppc0: [ITHREAD] > ppbus0: on ppc0 > -atrtc0: at port 0x70 irq 8 on isa0 > +atrtc0: at port 0x70 irq 8 on isa0 > +atrtc0: [FILTER] > +Event timer "RTC" frequency 32768 Hz quality 0 > +Starting kernel event timers: LAPIC @ 200Hz, RTC @ 128Hz > Timecounters tick every 5.000 msec Everything seems reasonable there. Try to collect more information: sysctl kern.timecounter sysctl kern.eventtimer vmstat -ia systat -vm 1 (presence and frequencies of interrupts) It could be a bug in emulation of some timers or bug in respective timer driver, which was not triggered before last changes. You may try switch to different timecounter by setting kern.timecounter.hardware, or different eventtimers by setting kern.eventtimer.timer1 and kern.eventtimer.timer2 sysctls. -- Alexander Motin