From owner-freebsd-stable@FreeBSD.ORG  Thu Mar 22 16:46:40 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CEAB5106566B;
	Thu, 22 Mar 2012 16:46:40 +0000 (UTC)
	(envelope-from c.kworr@gmail.com)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com
	[209.85.214.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 1F5F58FC19;
	Thu, 22 Mar 2012 16:46:39 +0000 (UTC)
Received: by bkcjc3 with SMTP id jc3so2612562bkc.13
	for <multiple recipients>; Thu, 22 Mar 2012 09:46:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	bh=e13DKC8JUDL4zP4tn36KhDhlHcNuExTKMzpRxXdQ8MM=;
	b=NIjonGtxmOR6zN4L9JVVo5axXqQ+QQCC5pbpm3ZgjR9xkOedX++QJ+LnGYpTzToCBp
	KaTtShvXf1WO/sqP+Q1oOXT+H/JPl/5YKYmZt3UgnzhV87G0iWyb0eNozj6NFn/4Zvhi
	sDlB8Sukpl1qa+tPzkcsle2O9xgu5wg/bGASDUiN4KRQFRpadUMqWAq3PEp7QfW0rJxZ
	U4vfzDtMsldMu3U84fw5D9yUvQviw9TJncYWq7sl3EI3ZVt1zSY3z4i+U8Fqhu2AzzxE
	ohNO6bl9eqTs+dkqaLszVew5Bm7zgr925F2lWxWjL4dpdW8heqnZ6JB7MxwbtkZv7B3Y
	+3OQ==
Received: by 10.204.132.80 with SMTP id a16mr3366588bkt.18.1332434798919;
	Thu, 22 Mar 2012 09:46:38 -0700 (PDT)
Received: from green.tandem.local (132-186-132-95.pool.ukrtel.net.
	[95.132.186.132])
	by mx.google.com with ESMTPS id v2sm10991488bki.7.2012.03.22.09.46.37
	(version=SSLv3 cipher=OTHER); Thu, 22 Mar 2012 09:46:38 -0700 (PDT)
Message-ID: <4F6B576B.7000803@gmail.com>
Date: Thu, 22 Mar 2012 18:46:35 +0200
From: Volodymyr Kostyrko <c.kworr@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:11.0) Gecko/20120315 Firefox/11.0 SeaMonkey/2.8
MIME-Version: 1.0
To: Andriy Gapon <avg@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>
In-Reply-To: <4F6B5459.4090401@FreeBSD.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 16:46:40 -0000

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.