Also seeing this on most recent Feisty. [EMAIL PROTECTED]:~# uname -a Linux user0 2.6.20-16-server #2 SMP Sun Sep 23 18:36:55 UTC 2007 x86_64 GNU/Linux
[EMAIL PROTECTED]:~# dmesg | grep -i throttling [ 81.146796] ACPI: Processor [CPU0] (supports 8 throttling states) [ 81.146847] ACPI: Processor [CPU1] (supports 8 throttling states) [ 81.146875] ACPI: Processor [CPU2] (supports 8 throttling states) [ 81.146930] ACPI: Processor [CPU3] (supports 8 throttling states) [ 81.146954] ACPI: Processor [CPU4] (supports 8 throttling states) [ 81.147009] ACPI: Processor [CPU5] (supports 8 throttling states) [ 81.147065] ACPI: Processor [CPU6] (supports 8 throttling states) [ 81.147110] ACPI: Processor [CPU7] (supports 8 throttling states) [EMAIL PROTECTED]:~# modprobe acpi-cpufreq FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.20-16-server/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): No such device [EMAIL PROTECTED]:~# cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU analyzing CPU 1: no or unknown cpufreq driver is active on this CPU ... [EMAIL PROTECTED]:~# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU L5320 @ 1.86GHz stepping : 7 cpu MHz : 1861.911 cache size : 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm bogomips : 3726.73 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: ... Can only speculate that they turned it off for server kernels? -- CPU Frequency Throttling not working on Xeon EM64T https://bugs.launchpad.net/bugs/163398 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
