Date: Thu, 22 Mar 2012 18:13:31 +0200 From: Volodymyr Kostyrko <c.kworr@gmail.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org, Mike Tkachuk <mike@tkachuk.name> Subject: Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0 Message-ID: <4F6B4FAB.1020202@gmail.com> In-Reply-To: <4F6B4B93.7020309@FreeBSD.org> References: <1977769407.20120322151934@tkachuk.name> <4F6B4030.5090907@FreeBSD.org> <4F6B4631.8020006@gmail.com> <4F6B4B93.7020309@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6B4FAB.1020202>