Date: Mon, 13 Mar 2023 18:10:38 +0000 From: void <void@f-m.fm> To: freebsd-hackers@freebsd.org Subject: Re: CPU supports Enhanced Speedstep, but is not recognized. Message-ID: <ZA9nHjfVszgaDy6l@int21h> In-Reply-To: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> References: <ZA9N4SFhoILqCeIr@int21h> <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 13, 2023 at 12:29:33PM -0400, mike tancsa wrote:
>On 3/13/2023 12:22 PM, void wrote:
>> The system is a HP ProLiant dual Xeon E5-2690 v2, so there are 40 "cpus"
>> ie 20 if hyperthreading is turned off, in total.
>>
>> I was kind of surprised this didn't work out-of-the-box considering
>> the age of the cpu, its use-context and how widely it was/is used
>> in that context. Clearly I'm doing something wrong or missing something.
>>
>> Should it work?
>>
>Is the hw pstate taking precedence perhaps ? What does
>
>sysctl -a dev.hwpstate_intel
>
>show ?
Think I might have found the answer in est(4):
###
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 471c471c0600471c
device_attach: est%d attach returned 6
Indicates all attempts to attach to this interface have failed. This
usually indicates an improper BIOS setting restricting O/S control of the
CPU speeds. Consult your BIOS documentation for more details.
###
so the next problem is out-of-band access, so not a freebsd problem.
Sorry for the noise.
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZA9nHjfVszgaDy6l>