HEADSUP: cpufreq import complete, acpi_throttling changed
Jiawei Ye
leafy7382 at gmail.com
Mon Feb 14 07:18:18 PST 2005
On Mon, 14 Feb 2005 15:23:19 +0100, Alexander Leidinger
<netchild at freebsd.org> wrote:
> I don't know if it is because of the cpufreq import. But because of the
> cpufreq import I've looked again at the acpi sysctl's and noticed this new
> state which wasn't there before. "Didn't work" means "the systems freezes
> hard, no keyboard interrupt is processed".
>
> Bye,
> Alexander.
I have a funny situation there. kldloading acpi_perf and then
unloading results in this:
leafy at chihiro:~$ sudo kldunload acpi_perf
kldunload: can't unload file: Device not configured
leafy at chihiro:~$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU1
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
leafy at chihiro:~$ dmesg -a |grep CPU
CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1816.99-MHz 686-class CPU)
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
Is this expected?
--
"Without the userland, the kernel is useless."
--inspired by The Tao of Programming
More information about the freebsd-acpi
mailing list