FreeBSD 12 – Powerd Profile Reverts and CPU Frequency Stays Low – Persistent Performance Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Application latency increases because CPU frequency governor remains in conservative state.

Environment & Reproduction

Observed after reboot when powerd is disabled or incorrectly parameterized.

service powerd onestatus
sysctl dev.cpu.0.freq

Root Cause Analysis

powerd startup settings do not enforce intended adaptive/high performance behavior.

Quick Triage

Check active governor behavior under synthetic load.

Step-by-Step Diagnosis

Inspect rc.conf powerd flags and CPU frequency transitions.

grep -E "powerd_enable|powerd_flags" /etc/rc.conf
sysctl dev.cpu | grep freq

Solution – Primary Fix

Enable powerd with explicit policy flags and restart service.

sysrc powerd_enable=YES
sysrc powerd_flags="-a hiadaptive -b adaptive"
service powerd restart

Solution – Alternative Approaches

Pin CPU frequency policy manually for deterministic benchmark environments.

Verification & Acceptance Criteria

CPU frequency scales appropriately under load and returns to baseline at idle.

Rollback Plan

Restore previous powerd flags if thermal or power constraints are exceeded.

Prevention & Hardening

Track governor settings in baseline audits and monitor frequency anomalies.

Related Errors & Cross-Refs

performance regression after reboot, CPU stuck at low freq.

Related tutorial: View the step-by-step tutorial for freebsd-12.

View all freebsd-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

powerd(8), cpufreq documentation, and FreeBSD performance tuning notes.