From owner-freebsd-current@FreeBSD.ORG Wed Jun 15 20:39:37 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 8EDB91065670; Wed, 15 Jun 2011 20:39:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "Ian FREISLICH" Date: Wed, 15 Jun 2011 16:39:26 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106151639.30308.jkim@FreeBSD.org> Cc: freebsd-current@FreeBSD.org 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: Wed, 15 Jun 2011 20:39:37 -0000 On Wednesday 15 June 2011 03:27 pm, Ian FREISLICH wrote: > > > 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? > > I have the same issue with my system (Atom N270). The effect that > I see is about 29 wall clock seconds are recorded as 1 system > second. Can please you send me output from the following? sh -c 'count=10; while [ $count -gt 0 ]; do count=$((count - 1));\ sysctl kern.timecounter; sleep 1; done' > I had do something similar to the OP to make my system useable since > it doesn't seem possible to influence timecounter choice at boot > time. You can just add the following line in /etc/sysctl.conf for now: kern.timecounter.hardware=HPET Jung-uk Kim