Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Mar 2006 08:03:02 +0100
From:      Wilko Bulte <wb@freebie.xs4all.nl>
To:        Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc:        Mike Jakubik <mikej@rogers.com>, freebsd-current@freebsd.org
Subject:   Re: Still seeing "calcru: runtime went backwards" messages
Message-ID:  <20060302070302.GB10564@freebie.xs4all.nl>
In-Reply-To: <15841.1141279248@critter.freebsd.dk>
References:  <200603011724.08214.jhb@freebsd.org> <15841.1141279248@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 02, 2006 at 06:00:48AM +0000, Poul-Henning Kamp wrote..
> In message <200603011724.08214.jhb@freebsd.org>, John Baldwin writes:
> 
> >Maybe we could make the dynamic flag for the tsc controllable via tunable?
> 
> Ideally ACPI would tell us the max TSC frequency and the TSC wouldn't need
> to be marked variable. Havn't had time to look at this yet though.
> 
> >If I have a server machine without any fancy pentium-m cpufreq type stuff,
> >then I would rather just use the tsc frequency snapshot taken at boot and
> >just stick with that as the static frequency then have a bunch of warnings
> >on the console if the max freq changes sometime later.
> 
> Right, I would actually prefer to try to make the calibration more precise
> first, rather than add yet another knob for roots to remember to tweak.
> 
> >Also, note that
> >I am still getting a bunch of the backwards messages on my DS20 Alpha which
> >is _not_ using the TSC. :)
> 
> That's interesting...  Alpha should be using the timecounter and that
> is not marked "variable".
> 
> My alpha hasn't been able to boot in a long time now :-(

Bah indeed.

Can't you get a DS10 from the ex-package-building cluster?  Kris
is not using those anymore so my guess(!!!) is that they are sitting idle.

-- 
Wilko Bulte				wilko@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060302070302.GB10564>