From owner-freebsd-stable@FreeBSD.ORG Fri Apr 18 18:13:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CC98106564A for ; Fri, 18 Apr 2008 18:13:04 +0000 (UTC) (envelope-from pertti.kosunen@pp.nic.fi) Received: from pne-smtpout3-sn2.hy.skanova.net (pne-smtpout3-sn2.hy.skanova.net [81.228.8.111]) by mx1.freebsd.org (Postfix) with ESMTP id 190C78FC0A for ; Fri, 18 Apr 2008 18:13:04 +0000 (UTC) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [10.0.0.20] (80.222.104.244) by pne-smtpout3-sn2.hy.skanova.net (7.3.129) id 478BDB9600562D80 for freebsd-stable@freebsd.org; Fri, 18 Apr 2008 19:03:21 +0200 Message-ID: <4808D466.8000508@pp.nic.fi> Date: Fri, 18 Apr 2008 20:03:34 +0300 From: Pertti Kosunen User-Agent: Thunderbird 2.0.0.9 (X11/20071123) MIME-Version: 1.0 To: freebsd-stable@freebsd.org 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> In-Reply-To: <20080418152957.GA44461@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: calcru: time went backwards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2008 18:13:04 -0000 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.