From owner-freebsd-current@FreeBSD.ORG Mon Jun 13 18:56:57 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 06E171065673; Mon, 13 Jun 2011 18:56:56 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Mon, 13 Jun 2011 14:56:34 -0400 User-Agent: KMail/1.6.2 References: <20110613184410.4f6e2b81@fabiankeil.de> In-Reply-To: <20110613184410.4f6e2b81@fabiankeil.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106131456.38038.jkim@FreeBSD.org> Cc: Subject: Re: Time keeping Issues with the low-resolution TSC timecounter X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2011 18:56:57 -0000 On Monday 13 June 2011 12:44 pm, Fabian Keil wrote: > I'm experiencing time-related issues that seem to be caused by > the low-resolution TSC timecounter (r222866). > > The problem I noticed first is that it takes unusually long until a > key press is repeated. With the default eventtimer (HPET) it seems > to take about 4s, which can be slightly improved by switching to > i8254. > > The "error beep" seems to take longer than usual, too, > and the system "feels sluggish" in general. > > An effect that is easier to measure is that the system is unable > to properly keep the time. Again the problem is less severe when > using i8254 instead of HPET: [SNIP] First of all, please do not mix timecounter issues with eventtimer. They are not directly related. Can you please show me verbose boot messages *without* your patch? Does "sysctl kern.timecounter.hardware=HPET" help *without* touching eventtimers? Jung-uk Kim