Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jun 2011 21:27:16 +0200
From:      "Ian FREISLICH" <ianf@clue.co.za>
To:        freebsd-current@FreeBSD.org
Cc:        Jung-uk Kim <jkim@FreeBSD.org>
Subject:   Re: Time keeping Issues with the low-resolution TSC timecounter
Message-ID:  <E1QWvkC-0001QH-Cj@clue.co.za>

next in thread | raw e-mail | index | archive | help
> > 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.
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.

Ian

-- 
Ian Freislich



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1QWvkC-0001QH-Cj>