SuperMicro i7 (UP) - very slow performance

Ian Smith smithi at nimnet.asn.au
Thu Sep 23 16:47:08 UTC 2010


On Thu, 23 Sep 2010, Alexander Motin wrote:

 > Date: Thu, 23 Sep 2010 19:42:29 +0300
 > From: Alexander Motin <mav at FreeBSD.org>
 > To: Ian Smith <smithi at nimnet.asn.au>
 > Cc: Bryce <bryce at bryce.net>, FreeBSD Stable <freebsd-stable at 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


More information about the freebsd-stable mailing list