Date: Thu, 22 Mar 2012 18:46:35 +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: <4F6B576B.7000803@gmail.com> In-Reply-To: <4F6B5459.4090401@FreeBSD.org> References: <1977769407.20120322151934@tkachuk.name> <4F6B4030.5090907@FreeBSD.org> <4F6B4631.8020006@gmail.com> <4F6B4B93.7020309@FreeBSD.org> <4F6B4FAB.1020202@gmail.com> <4F6B5459.4090401@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Gapon wrote: >> 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. I'm sorry, I totally misunderstood the meaning of this tunable. Its unclear from man page which value enables or disables periodic code. -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6B576B.7000803>