Date: Fri, 18 Apr 2008 20:03:34 +0300 From: Pertti Kosunen <pertti.kosunen@pp.nic.fi> To: freebsd-stable@freebsd.org Subject: Re: calcru: time went backwards Message-ID: <4808D466.8000508@pp.nic.fi> In-Reply-To: <20080418152957.GA44461@eos.sc1.parodius.com> References: <00df01c89ef8$9733c6d0$c59b5470$@org> <20080415141138.GA33154@mail.scottro.net> <20080415142034.GA80792@eos.sc1.parodius.com> <20080415225159.R54132@thebighonker.lerctr.org> <4808A776.60503@pp.nic.fi> <20080418152957.GA44461@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote: >> 7.0-RELEASE (AMD64) didn't have this problem. > > Are you absolutely positive about this (re: amd64 not having the > problem)? I can reproduce the issue documented in my Wiki page on i386 > or amd64. The piece that seems to cause it, at least in the case of the > PDSMI+, is EIST being enabled in the BIOS. Yes, with 7.0-RELEASE speedstep was working and there was no "calcru: runtime went backwards..." messages. But i did have cpufreq compiled in kernel.. It seems to be working now when loaded as module from loader.conf.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4808D466.8000508>