Date: Fri, 22 Jun 2012 12:52:21 +0200 From: Maciej Suszko <maciej@suszko.eu> To: Alexander Churanov <freebsd@alexanderchuranov.com> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/166549: [eventttimers] Clock stops ticking in some cases with new timer framework in 9 Message-ID: <20120622125221.6af08bb1@helium> In-Reply-To: <201204270950.q3R9oAVJ062719@freefall.freebsd.org> References: <201204270950.q3R9oAVJ062719@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120622125221.6af08bb1>