From owner-freebsd-stable@FreeBSD.ORG Fri Apr 18 15:29:57 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 4002C106566C for ; Fri, 18 Apr 2008 15:29:57 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2B0498FC25 for ; Fri, 18 Apr 2008 15:29:57 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 10EAD1CC033; Fri, 18 Apr 2008 08:29:57 -0700 (PDT) Date: Fri, 18 Apr 2008 08:29:57 -0700 From: Jeremy Chadwick To: Pertti Kosunen Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4808A776.60503@pp.nic.fi> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org 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 15:29:57 -0000 On Fri, Apr 18, 2008 at 04:51:50PM +0300, Pertti Kosunen wrote: > Larry Rosenman wrote: >> On Tue, 15 Apr 2008, Jeremy Chadwick wrote: >>> And what the FAQ doesn't cover is here: >>> >>> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues >>> >>> * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ >>> motherboards (and possibly others) >>> * Symptom: kernel outputs messages like kernel: calcru: negative >>> runtime of -XXXXX usec for pid XX >>> * Workaround: Disable the EIST feature in the BIOS. You can still >>> achieve ACPI-based processor >>> frequency throttling by using powerd(8). >>> * Reference: >>> http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html >> What I find interesting is I hadn't seen these until this kernel update :( > > Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq > module is loaded. > > 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. For example, this is my a PDSMI+ system (amd64), which exhibits the problem (when EIST is enabled). EIST in the BIOS is disabled here: est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est0 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est1 attach returned 6 powerd(8) is running and working perfectly, as shown below. Look closely at dev.cpu.0.freq and freq_levels: # ps -auxw | grep powerd root 714 0.0 0.1 5628 1172 ?? Ss Wed04AM 0:10.08 /usr/sbin/powerd -p 2000 # sysctl -a | grep dev.cpu.0.freq dev.cpu.0.freq: 297 dev.cpu.0.freq_levels: 2382/-1 2084/-1 1786/-1 1488/-1 1191/-1 893/-1 595/-1 297/-1 Under heavy load, the frequency gradually steps/climbs to 2382MHz as expected. During this time, absolutely no negative runtime messages appear (and have never appeared). If I reboot the box, enable EIST in the BIOS, and start FreeBSD, negative runtime messages begin almost immediately. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |