On Thu, Sep 15, 2011 at 9:22 PM, Andriy Gapon <avg_at_freebsd.org> wrote: > on 15/09/2011 19:20 Arnaud Lacombe said the following: >> est0: failed to enable SpeedStep >> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >> est1: failed to enable SpeedStep >> p4tcc1: <CPU Frequency Thermal Control> on cpu1 >> est2: failed to enable SpeedStep >> p4tcc2: <CPU Frequency Thermal Control> on cpu2 >> est3: failed to enable SpeedStep >> p4tcc3: <CPU Frequency Thermal Control> on cpu3 >> est4: failed to enable SpeedStep >> p4tcc4: <CPU Frequency Thermal Control> on cpu4 >> est5: failed to enable SpeedStep >> p4tcc5: <CPU Frequency Thermal Control> on cpu5 >> est6: failed to enable SpeedStep >> p4tcc6: <CPU Frequency Thermal Control> on cpu6 >> est7: failed to enable SpeedStep >> p4tcc7: <CPU Frequency Thermal Control> on cpu7 >> >> It feels strange that the latest FreeBSD do not support est(4) on a 3 >> years old CPU... > > Somehow I do not read "failed to enable" as "can not detect" or "can not > support" SpeedStep on this CPU. sys/x86/cpufreq/est.c:1008 /* Attempt to enable SpeedStep if not currently enabled. */ msr = rdmsr(MSR_MISC_ENABLE); if ((msr & MSR_SS_ENABLE) == 0) { wrmsr(MSR_MISC_ENABLE, msr | MSR_SS_ENABLE); if (bootverbose) device_printf(dev, "enabling SpeedStep\n"); /* Check if the enable failed. */ msr = rdmsr(MSR_MISC_ENABLE); if ((msr & MSR_SS_ENABLE) == 0) { device_printf(dev, "failed to enable SpeedStep\n"); return (ENXIO); } } Andriy - He is correct. Possibly power management on server processors isn't considered a priority by the maintainer.Received on Thu Sep 15 2011 - 17:32:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:17 UTC