From owner-freebsd-bugs@FreeBSD.ORG  Fri Jun 22 10:52:30 2012
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CB60A106566B
	for <freebsd-bugs@FreeBSD.org>; Fri, 22 Jun 2012 10:52:30 +0000 (UTC)
	(envelope-from maciej@suszko.eu)
Received: from smtp.suszko.eu (tlhscd-1-pt.tunnel.tserv6.fra1.ipv6.he.net
	[IPv6:2001:470:1f0a:e2c::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 81AE88FC14
	for <freebsd-bugs@FreeBSD.org>; Fri, 22 Jun 2012 10:52:30 +0000 (UTC)
Received: from ibox (localhost [127.0.0.1])
	by smtp.suszko.eu (Postfix) with ESMTP id C21182059E0;
	Fri, 22 Jun 2012 12:52:22 +0200 (CEST)
X-Virus-Scanned: YES, Passed
Received: from smtp.suszko.eu ([127.0.0.1])
	by ibox (mail.suszko.eu [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id ROYtkChPbQCL; Fri, 22 Jun 2012 12:52:22 +0200 (CEST)
Received: from helium (biuro.easygo.pl [81.95.206.139])
	by smtp.suszko.eu (Postfix) with ESMTPSA id 5397C2059C4;
	Fri, 22 Jun 2012 12:52:22 +0200 (CEST)
Date: Fri, 22 Jun 2012 12:52:21 +0200
From: Maciej Suszko <maciej@suszko.eu>
To: Alexander Churanov <freebsd@alexanderchuranov.com>
Message-ID: <20120622125221.6af08bb1@helium>
In-Reply-To: <201204270950.q3R9oAVJ062719@freefall.freebsd.org>
References: <201204270950.q3R9oAVJ062719@freefall.freebsd.org>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: kern/166549: [eventttimers] Clock stops ticking in some cases
 with new timer framework in 9
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 10:52:30 -0000

Same behavior on my VPS (KVM-based):

Output of 'uname -a':
FreeBSD archeo 9.0-RELEASE-p1 FreeBSD 9.0-RELEASE-p1 #0: Tue May 22 12:46:09 CEST 2012     root@archeo:/usr/obj/usr/src/sys/ARCHEO  i386

Output of 'sysctl kern.timecounter': http://pastebin.com/GrGD5sZj
Output of 'sysctl kern.eventtimer': http://pastebin.com/Xg5zgT18
Output of 'dmesg -a': http://pastebin.com/VgLGuGD6

Setting kern.eventtimer.periodic to 1 starts the clock again. When set
to 0 and clock is stopped, machine is fully accessed via SSH, which if
you going to restart is going to hang somehow. All timer-based actions
fail of course (cron is not running any tasks, sleep(1) lasts forever,
load average does not change etc.).
-- 
regards, Maciej Suszko.