From owner-freebsd-stable@FreeBSD.ORG Thu Mar 22 16:33:33 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 51709106566C for ; Thu, 22 Mar 2012 16:33:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 98C108FC0A for ; Thu, 22 Mar 2012 16:33:32 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA10991; Thu, 22 Mar 2012 18:33:30 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <4F6B5459.4090401@FreeBSD.org> Date: Thu, 22 Mar 2012 18:33:29 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120221 Thunderbird/10.0.2 MIME-Version: 1.0 To: Volodymyr Kostyrko References: <1977769407.20120322151934@tkachuk.name> <4F6B4030.5090907@FreeBSD.org> <4F6B4631.8020006@gmail.com> <4F6B4B93.7020309@FreeBSD.org> <4F6B4FAB.1020202@gmail.com> In-Reply-To: <4F6B4FAB.1020202@gmail.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Mike Tkachuk Subject: Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 16:33:33 -0000 on 22/03/2012 18:13 Volodymyr Kostyrko said the following: > Andriy Gapon wrote: >> on 22/03/2012 17:33 Volodymyr Kostyrko said the following: >>> Andriy Gapon wrote: >>>> on 22/03/2012 15:19 Mike Tkachuk said the following: >>>>> kern.eventtimer.periodic: 0 >>>> >>>> It might make sense to try 1 here. >>>> Also you could attempt to involve mav@ directly - here is an author of the code >>>> and an expert on it. >>> >>> Better ask before setting as this doubles hpet0 (with HPET) or cpu0:timer (with >>> LAPIC) interrupt rate for me. >> >> Does it make your system unusable? >> Are you comparing with pre-eventtimers version of FreeBSD? > > In short term - no. Haven't tested it thoroughly. Results are the same (double > interrupt rate according to `systat 1 -v`) for: > * i386 and amd64 9-STABLE; > * amd64 9.0. No comment. > As everything related to timing/freq/acpi can be unpredictive I wouldn't recommend > this to anyone. I own at least two Intel CPU's failing somewhere near timing/apic > when loading cpufreq and enabling powerd. > What exactly you wouldn't recommend? Let's not introduce unrelated topics and vague uncertainties. Setting kern.eventtimer.periodic to 1 makes eventtimer subsystem to behave less efficiently but more similar to the pre-eventtimer code. So this is #1 suggestion when people run into some new problems with eventtimers. Which is what this thread is about. -- Andriy Gapon