From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:36:26 2010 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 2DD0E106566B; Thu, 23 Sep 2010 16:36:26 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6E38FC1B; Thu, 23 Sep 2010 16:36:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8NGaHeI021629; Fri, 24 Sep 2010 02:36:18 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Sep 2010 02:36:17 +1000 (EST) From: Ian Smith To: Alexander Motin In-Reply-To: <4C9B0F2C.20601@FreeBSD.org> Message-ID: <20100924022558.T11124@sola.nimnet.asn.au> References: <4C9B0F2C.20601@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Stable , Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance 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: Thu, 23 Sep 2010 16:36:26 -0000 On Thu, 23 Sep 2010, Alexander Motin wrote: > Bryce wrote: > > I don't think it is temperature, I have never seen temps above the low > > 60's C and the speed never goes down from 2.8 Ghz. This is what I see > > when running your dd for a while: > > > > bryce@tahiti[~]>sysctl -a | grep temperature > > dev.cpu.0.temperature: 55.0C > > dev.cpu.1.temperature: 55.0C > > dev.cpu.2.temperature: 51.0C > > dev.cpu.3.temperature: 52.0C > > dev.cpu.4.temperature: 59.0C > > dev.cpu.5.temperature: 61.0C > > dev.cpu.6.temperature: 51.0C > > dev.cpu.7.temperature: 52.0C > > bryce@tahiti[~]>sysctl -n dev.cpu.0.freq > > 2801 > > Looks not bad, but I would checked it during good compilation, using all > cores. > > Just to compare, my Core i7-870 with boxed cooler reports: > 31C being idle with tuned power management, > 53C being idle without any power management, > 85C during `make -j16`. > That system did `make -j16 universe` in about 3 hours AFAIR. > > PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered due > to overheating. Thanks, I've often wondered about that (among other things :) So not looking much like overheating. But don't these messages requoted below seem at all significant? At least, I've never seen them before: > est0: on cpu0 > est0: Invalid id16 (set, cur) = (20, 21) > est0: Can't check freq 2667, it may be invalid > est0: Invalid id16 (set, cur) = (19, 21) > est0: Can't check freq 2533, it may be invalid > est0: Invalid id16 (set, cur) = (18, 21) > est0: Can't check freq 2400, it may be invalid > est0: Invalid id16 (set, cur) = (17, 21) > est0: Can't check freq 2267, it may be invalid > est0: Invalid id16 (set, cur) = (16, 21) > est0: Can't check freq 2133, it may be invalid > est0: Invalid id16 (set, cur) = (15, 21) > est0: Can't check freq 2000, it may be invalid > est0: Invalid id16 (set, cur) = (14, 21) > est0: Can't check freq 1867, it may be invalid > est0: Invalid id16 (set, cur) = (13, 21) > est0: Can't check freq 1733, it may be invalid > est0: Invalid id16 (set, cur) = (12, 21) > est0: Can't check freq 1600, it may be invalid cheers, Ian