Bug 140658

Summary:	[cpufreq] dev.cpu.0.cx_lowest=C3 from /etc/sysctl.conf or /boot/loader.conf does not apply at boot when cpufreq used as module outside kernel
Product:	Base System	Reporter:	Slawomir Wojciech Wojtczak <vermaden>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed Overcome By Events
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Slawomir Wojciech Wojtczak 2009-11-18 07:20:02 UTC

If you have cpufreq compiled into the kernel, then setting C-states
from /etc/sysctl.conf or /boot/loader.conf works as desired.

examples:
  /etc/sysctl.conf
  dev.cpu.0.cx_lowest=C2
  dev.cpu.0.cx_lowest=C3

  /boot/loader.conf
  cpufreq_load="YES"
  dev.cpu.0.cx_lowest=C2
  dev.cpu.0.cx_lowest=C3

When you tak cpufreq OUTSIDE the kernel, as a module, these
setting no longer apply after reboot, but you can manually set
them by sysctl(8) as usual.

Of course cpufreq is loaded at boot with cpufreq_load="YES" line in
/boot/loader.conf

Comment 1 Eitan Adler freebsd_committer

2017-12-31 07:59:27 UTC

For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped

Comment 2 Slawomir Wojciech Wojtczak 2018-05-24 08:54:16 UTC

Too old, nobody would reproduce it now ...