Date: Fri, 24 Sep 2010 02:47:01 +1000 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Alexander Motin <mav@FreeBSD.org> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org>, Bryce <bryce@bryce.net> Subject: Re: SuperMicro i7 (UP) - very slow performance Message-ID: <20100924024527.M11124@sola.nimnet.asn.au> In-Reply-To: <4C9B8375.4070505@FreeBSD.org> References: <mailpost.1285173904.332223.70365.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw> <mailpost.1285202775.8039756.86645.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw> <4C9B0F2C.20601@FreeBSD.org> <20100924022558.T11124@sola.nimnet.asn.au> <4C9B8375.4070505@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Sep 2010, Alexander Motin wrote: > Date: Thu, 23 Sep 2010 19:42:29 +0300 > From: Alexander Motin <mav@FreeBSD.org> > To: Ian Smith <smithi@nimnet.asn.au> > Cc: Bryce <bryce@bryce.net>, FreeBSD Stable <freebsd-stable@FreeBSD.org> > 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: <Enhanced SpeedStep Frequency Control> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100924024527.M11124>