From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:47:08 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 74E7E1065672; Thu, 23 Sep 2010 16:47:08 +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 E17968FC08; Thu, 23 Sep 2010 16:47:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8NGl1Nv022246; Fri, 24 Sep 2010 02:47:01 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Sep 2010 02:47:01 +1000 (EST) From: Ian Smith To: Alexander Motin In-Reply-To: <4C9B8375.4070505@FreeBSD.org> Message-ID: <20100924024527.M11124@sola.nimnet.asn.au> References: <4C9B0F2C.20601@FreeBSD.org> <20100924022558.T11124@sola.nimnet.asn.au> <4C9B8375.4070505@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:47:08 -0000 On Thu, 23 Sep 2010, Alexander Motin wrote: > Date: Thu, 23 Sep 2010 19:42:29 +0300 > From: Alexander Motin > To: Ian Smith > Cc: Bryce , FreeBSD Stable > Subject: Re: SuperMicro i7 (UP) - very slow performance > > Ian Smith wrote: > > 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 > > They are not. It is specifics of EIST behavior on multicore CPUs. It is > impossible to test P-states during driver attach (before AP CPUs > started). I have already disabled this check for SMP systems. Ok, thanks. That's me out of ideas .. but lurking with interest. cheers, Ian