In BIOS, the system sees the CPU at 1,66 Ghz frequency, which is the correct maximum frequency for an Atom D510 CPU. However, upon finishing the boot process, without any tunables, the CPU gets stuck at the wrong frequency: dev.cpu.0.freq: 1249 Mhz, severely degrading performance.
Enabling and starting powerd and then putting the system under load will put the CPU to the correct frequency: dev.cpu.0.freq: 1666, however powerd seems to misbehave as well: After the initial frequency increase of the CPU to 1666 Mhz, the CPU gets stuck at this clockrate. Sometimes powerd will work correctly for a minute or so, correctly adjusting the CPU frequency according to load, but in a very short time, the CPU will get stuck at 1666 Mhz permanently (until reboot).
Changing from "highadaptive" to "adaptive" mode in powerd settings seems to have no effect on this behaviour. I've also made a PR for this issue, containing both my dmesg and output of sysctl -a | grep acpi here: http://www.freebsd.org/cgi/query-pr.cgi?pr=144551
Any ideas?
Enabling and starting powerd and then putting the system under load will put the CPU to the correct frequency: dev.cpu.0.freq: 1666, however powerd seems to misbehave as well: After the initial frequency increase of the CPU to 1666 Mhz, the CPU gets stuck at this clockrate. Sometimes powerd will work correctly for a minute or so, correctly adjusting the CPU frequency according to load, but in a very short time, the CPU will get stuck at 1666 Mhz permanently (until reboot).
Changing from "highadaptive" to "adaptive" mode in powerd settings seems to have no effect on this behaviour. I've also made a PR for this issue, containing both my dmesg and output of sysctl -a | grep acpi here: http://www.freebsd.org/cgi/query-pr.cgi?pr=144551
Any ideas?