Cpu frequency scaling is limited to stock speeds

Hi litemotiv,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you with the 7.10 Gutsy Gibbon release? You can download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download . Please report back your results. Thanks!

Hi Leann,

Thank you for taking the time to check up on this bug. The problem still persists on 7.10 Gutsy and Hardy Pre-Alpha which i am currently using:

2.6.22-14-generic #1 SMP
cpufreqd 2.2.1-2

[changing stock speed of 2.4ghz to 3ghz in bios]

> cpufreq-set -g userspace
> cpufreq-set -u 3000000
> cpufreq-set -f 3000000

> cpufreq-info

analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1.60 GHz - 2.39 GHz
  available frequency steps: 2.39 GHz, 1.60 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance
  current policy: frequency should be within 1.60 GHz and 2.39 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 2.39 GHz (asserted by call to hardware).

analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 1.60 GHz - 2.39 GHz
  available frequency steps: 2.39 GHz, 1.60 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance
  current policy: frequency should be within 1.60 GHz and 2.39 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz (asserted by call to hardware).

Thanks for the update. I'm opened a new task against the actively developed kernel. However, I'm closing the report against linux-source-2.6.22 as it does not meet the criteria for a stable release update. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Hi litemotiv,

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. I wasn't sure if this was in fact the kernel you were using when you said you were running "Hardy Pre Alpha". Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Hi Leann,

I have tried 2.6.24-1 as you requested. The new kernel gives a lot of problems at this stage (i can't get X starting properly for instance), so i did some preliminary tests from the command line.

So far it seems like the bug still exists: cpufreq says the hardware limit is 2.39ghz, even though the processor did get properly detected as 3ghz by the kernel during boot. Apparently cpufreq uses the stock-values reported by the cpu rather than the actual speed that was detected by the kernel?

Best regards,
-lite.

I have the same kind of problem with this cpu (see bugreport https://bugs.launchpad.net/bugs/175310):
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 36
model name : AMD Turion(tm) 64 Mobile Technology ML-34
stepping : 2
cpu MHz : 1800.210
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni lahf_lm ts fid vid ttp tm stc
bogomips : 3603.94
clflush size : 64

Now, how can I disable the cpufreq module loading at startup?
By manually doing this:
sudo cpufreq-set -g performance #sets max cpu speed correctly
sudo modprobe -r powernow_k8
I permanently get the max cpu speed, as I (often) need. Note that the first step works because generally the max frequency reported by cpufreq-info is correct just after pc startup.

If that can help, I've just noted that frequency scaling works correctly (on my machine) with the linux kernel as provided by OpenSUSE 10.3:
#uname -r
2.6.22.5-31-default

Loading acer_acpi and wmi-acer modules seems to have solved the problem completely.

This bug still exists in the hardy alpha 5 kernel....

Frequency scaling on over clocked Core 2 Duo processors does not use the reported speed, but the original stockspeeds, while the Windows implementation of speedstep does work right.

Any comments of the dev's ?

Running overclocked 45nm Intel Core 2 Duo, E8400, kernel 2.6.22-14, Gutsy. Speedstep not working.

frank@sunshine:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
stepping : 6
cpu MHz : 4005.091
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
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 smx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 8015.16
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

One of the two cores. Works in WinXP, not in Ubuntu. Cores work at max speed only.

I would just like to add that my stock Intel Core 2 Duo e8400 runs only at max speed and states that scaling is unsupported with this CPU.

Can confirm with a E8500 clocked to 3.8Ghz with a Gigabyte-P35 board. Chugs along fine, but only at the maximum clock -- no speedstep.

simon@aristurtle:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
stepping : 6
cpu MHz : 3799.996
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
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 pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm
bogomips : 7604.46
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
stepping : 6
cpu MHz : 3799.996
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
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 pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm
bogomips : 7599.98
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Sorry: should say that I'm on Gutsy running Hardy's 2.6.24-11-generic kernel.

i would like to add to the comments that i have an hp dv2756 laptop and there is no frequency scalling.

this is running a stock T9300 processor. will not load the acpi_cpufreq module. earlier i have checked the bios by de/reconstructing using intel's compiler and it gave no errors.

attached dmesg hoping that somehow helps.

running gutsy gibbon with stock kernel, latest update

I'm having the same problem - first thought it was a specific problem with dual core processors and opened a bug (#213119).
After seeing this thread I went back to stock speed and voilla - cpu scaling works...

cpu is dual core E2200
mobo is gigabyte ga-p35-ds3l
distro is hardy beta, kernel is 2.6.24-15-generic. had the same prob with gutsy though (kernels 2.6.15-2.6.22).
scaling when O/C works well on XP.

The problem is again here with fresh new Hardy setup:
# uname -r
2.6.24-16-generic

# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 36
model name : AMD Turion(tm) 64 Mobile Technology ML-34
stepping : 2
cpu MHz : 1800.000
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni lahf_lm ts fid vid ttp tm stc
bogomips : 3603.93
clflush size : 64

Linux cpuscaling also works with gobolinux vanilla kernel.

I can reproduce this: a non-overclocked Core 2 Duo E8500 running Hardy has two speeds available: 2.00 GHz and 3.00 GHz. The actual speed of 3.16GHz can only be obtained by disabling frequency scaling in the BIOS settings.

$ cpufreq-infocpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 2.00 GHz - 3.00 GHz
  available frequency steps: 3.00 GHz, 2.00 GHz
  available cpufreq governors: userspace, powersave, ondemand, conservative, performance
  current policy: frequency should be within 2.00 GHz and 3.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz.
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 2.00 GHz - 3.00 GHz
  available frequency steps: 3.00 GHz, 2.00 GHz
  available cpufreq governors: userspace, powersave, ondemand, conservative, performance
  current policy: frequency should be within 2.00 GHz and 3.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz.

Yet another complaint about the CPU scaling! Why is it so difficult for the Ubuntu devs to get this working out-of-box? This problem has been around for as long as i have used Ubuntu (since 5.10), why is it such a big deal to add cpufrequtils to the standard install? Come on, get it sorted for once and for all!

Here is my /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.73GHz
stepping : 8
cpu MHz : 798.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2
bogomips : 1598.17
clflush size : 64

Same with me: Gigabyte EP35-DS3R with Core 2 Duo E8400 (stock freq 3.0 GHz) - cpufreq scaling works as expected.

When the frequency is manually increased (I tried 400 with multiplier of 9), cpufreq module does not even load - i.e. no frequence scaling available.

I can reproduce this: a non-overclocked Core 2 Duo Quad Q8600 running Hardy has two speeds available: 1.66 GHz and 2.39GHz. The actual speed of 3.01 or 3.5 GHz can only be obtained by disabling frequency scaling in the BIOS settings.

Pretty painful for those of us using it for scientific computing where a Ghz ifference is hours. Please let us know if there is a fix. It is not a hardware issue, as in Windows it works fine.

Just to add I am running 8.04 current to 7/24/08. If you could please give us some insight we would really appreciate it.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I quickly tried out Xubuntu Intrepid Ibex 8.10 Alpha5 Live CD and there is still no frequency scaling with my overclocked E6600 on a Gigabyte 965P-DS4 (works under Windows XP). Frequency scaling however works as soon as I switch back to stock speeds in BIOS and reboot the LiveCD.

-> issue remains

I just tried this on Kubuntu Intrepid Ibex, kernel 2.6.27-3 with my Asus P5W DH Deluxe mainboard with a Pentium Dual Core E2180 CPU. Frequency scaling doesn't work, neither with stock speeds nor when overclocking. Same issue existed also with the most recent Hardy kernel a couple of days ago.

Same issue remains in Intrepid Ibex too -- check bug #286133.

Is there any progress on this? I have the same problem with a Q6600 (which uses to E6600 chips) on Intrepid with 2.6.27-7-generic.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Could anyone please explain what happened to this bug, and why?

This problem occurs with NON-overclocked Core 2 Duo 8500 (3.16 GHz) on a stock Intel board that does not even support overclocking in the first place.

Just updating the CPU to a spiffier one (on fully-patched Hardy Heron x86) brought up the warning dialog box and forced the box to run on 100% CPU speed on both CPUs, effectively nulling the original upgrade goal (get a cooler-idling 45 nm technology CPU which still gives you the extra punch over the previous generation CPU when needed).

Ignoring such a relevant feature on top-end HW and top-end SW (Ubuntu) seems like a bad idea, especially when same board with Windows works just fine, even in overclocked situations (based on comments above).

Quick search did not bring up any guidance on how to work around this using manual config of speedstep, except by minimizing daily Ubuntu usage on dual-boot boxes.

Installing cpufrequtils did not help either.

I have to pull back my earlier astonishment a bit:

I upgraded the BIOS on the system, and now Speedstep is back.

So ignore the rant-ish above. Clearly there are deeper issues than just Linux kernel at play...

Does this mean that the BIOS upgrade fixed your problems?

Testing with the latest pre-release of Jaunty 9.04 will also help us identify if this exists in the latest upcoming release. Refer to http://www.ubuntu.com/testing/jaunty/beta . Please let us know.

Hi all,

I've just tested this week-end with a Jaunty up-to-date. The frequency
scaling worked, it was only the value displayed by the kernel that is wrong.
In /proc/cpuinfo, I could read the stock value for cpu speed, whereas the
bogomips was changed !

JV

2009/4/14 Amit Kucheria <email address hidden>

> Testing with the latest pre-release of Jaunty 9.04 will also help us
> identify if this exists in the latest upcoming release. Refer to
> http://www.ubuntu.com/testing/jaunty/beta . Please let us know.
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> Cpu frequency scaling is limited to stock speeds
> https://bugs.launchpad.net/bugs/132403
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Theory is where you know everything, but nothing works; practice is where
everything works, but nobody knows why. Here we combine theory with
practice; nothing works and nobody knows why !
A.Einstein

Can you provide details of your processor, your cpufreq driver and governor?

On Tue, Apr 14, 2009 at 09:27:01AM -0000, Jeremy Vies wrote:
> Hi all,
>
> I've just tested this week-end with a Jaunty up-to-date. The frequency
> scaling worked, it was only the value displayed by the kernel that is wrong.
> In /proc/cpuinfo, I could read the stock value for cpu speed, whereas the
> bogomips was changed !
>
> JV
>
> 2009/4/14 Amit Kucheria <email address hidden>
>
> > Testing with the latest pre-release of Jaunty 9.04 will also help us
> > identify if this exists in the latest upcoming release. Refer to
> > http://www.ubuntu.com/testing/jaunty/beta . Please let us know.
> >
> > ** Changed in: linux (Ubuntu)
> > Status: Triaged => Incomplete
> >
> > --
> > Cpu frequency scaling is limited to stock speeds
> > https://bugs.launchpad.net/bugs/132403
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Theory is where you know everything, but nothing works; practice is where
> everything works, but nobody knows why. Here we combine theory with
> practice; nothing works and nobody knows why !
> A.Einstein
>
> --
> Cpu frequency scaling is limited to stock speeds
> https://bugs.launchpad.net/bugs/132403
> You received this bug notification because you are a member of Ubuntu
> Kernel Team, which is subscribed to linux-source-2.6.22 in ubuntu.

--
----------------------------------------------------------------------
Amit Kucheria, Kernel Engineer || <email address hidden>
----------------------------------------------------------------------

I've got a core2duo e7300. It runs normally at 2.66GHz (10*266). I've just
changed FSB to 333.
I use Ubuntu out of box settings, so I think it's ondemand.

2009/4/14 Amit Kucheria <email address hidden>

> Can you provide details of your processor, your cpufreq driver and
> governor?
>
> On Tue, Apr 14, 2009 at 09:27:01AM -0000, Jeremy Vies wrote:
> > Hi all,
> >
> > I've just tested this week-end with a Jaunty up-to-date. The frequency
> > scaling worked, it was only the value displayed by the kernel that is
> wrong.
> > In /proc/cpuinfo, I could read the stock value for cpu speed, whereas the
> > bogomips was changed !
> >
> > JV
> >
> > 2009/4/14 Amit Kucheria <email address hidden>
> >
> > > Testing with the latest pre-release of Jaunty 9.04 will also help us
> > > identify if this exists in the latest upcoming release. Refer to
> > > http://www.ubuntu.com/testing/jaunty/beta . Please let us know.
> > >
> > > ** Changed in: linux (Ubuntu)
> > > Status: Triaged => Incomplete
> > >
> > > --
> > > Cpu frequency scaling is limited to stock speeds
> > > https://bugs.launchpad.net/bugs/132403
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> >
> >
> > --
> > Theory is where you know everything, but nothing works; practice is where
> > everything works, but nobody knows why. Here we combine theory with
> > practice; nothing works and nobody knows why !
> > A.Einstein
> >
> > --
> > Cpu frequency scaling is limited to stock speeds
> > https://bugs.launchpad.net/bugs/132403
> > You received this bug notification because you are a member of Ubuntu
> > Kernel Team, which is subscribed to linux-source-2.6.22 in ubuntu.
>
> --
> ----------------------------------------------------------------------
> Amit Kucheria, Kernel Engineer || <email address hidden>
> ----------------------------------------------------------------------
>
> --
> Cpu frequency scaling is limited to stock speeds
> https://bugs.launchpad.net/bugs/132403
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Theory is where you know everything, but nothing works; practice is where
everything works, but nobody knows why. Here we combine theory with
practice; nothing works and nobody knows why !
A.Einstein

Hmm.. I don't see any changes to bogomips in my /proc/cpuinfo when I change the frequency from the frequency-applet

Only my cpu MHz value changes.

On Tue, Apr 14, 2009 at 10:34:08AM -0000, Jeremy Vies wrote:
> I've got a core2duo e7300. It runs normally at 2.66GHz (10*266). I've just
> changed FSB to 333.
> I use Ubuntu out of box settings, so I think it's ondemand.
>
>
> 2009/4/14 Amit Kucheria <email address hidden>
>
> > Can you provide details of your processor, your cpufreq driver and
> > governor?
> >
> > On Tue, Apr 14, 2009 at 09:27:01AM -0000, Jeremy Vies wrote:
> > > Hi all,
> > >
> > > I've just tested this week-end with a Jaunty up-to-date. The frequency
> > > scaling worked, it was only the value displayed by the kernel that is
> > wrong.
> > > In /proc/cpuinfo, I could read the stock value for cpu speed, whereas the
> > > bogomips was changed !
> > >
> > > JV
> > >
> > > 2009/4/14 Amit Kucheria <email address hidden>
> > >
> > > > Testing with the latest pre-release of Jaunty 9.04 will also help us
> > > > identify if this exists in the latest upcoming release. Refer to
> > > > http://www.ubuntu.com/testing/jaunty/beta . Please let us know.
> > > >
> > > > ** Changed in: linux (Ubuntu)
> > > > Status: Triaged => Incomplete
> > > >
> > > > --
> > > > Cpu frequency scaling is limited to stock speeds
> > > > https://bugs.launchpad.net/bugs/132403
> > > > You received this bug notification because you are a direct subscriber
> > > > of the bug.
> > > >
> > >
> > >
> > > --
> > > Theory is where you know everything, but nothing works; practice is where
> > > everything works, but nobody knows why. Here we combine theory with
> > > practice; nothing works and nobody knows why !
> > > A.Einstein
> > >
> > > --
> > > Cpu frequency scaling is limited to stock speeds
> > > https://bugs.launchpad.net/bugs/132403
> > > You received this bug notification because you are a member of Ubuntu
> > > Kernel Team, which is subscribed to linux-source-2.6.22 in ubuntu.
> >
> > --
> > ----------------------------------------------------------------------
> > Amit Kucheria, Kernel Engineer || <email address hidden>
> > ----------------------------------------------------------------------
> >
> > --
> > Cpu frequency scaling is limited to stock speeds
> > https://bugs.launchpad.net/bugs/132403
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Theory is where you know everything, but nothing works; practice is where
> everything works, but nobody knows why. Here we combine theory with
> practice; nothing works and nobody knows why !
> A.Einstein
>
> --
> Cpu frequency scaling is limited to stock speeds
> https://bugs.launchpad.net/bugs/132403
> You received this bug notification because you are a member of Ubuntu
> Kernel Team, which is subscribed to linux-source-2.6.22 in ubuntu.

--
----------------------------------------------------------------------
Amit Kucheria, Kernel Engineer || <email address hidden>
----------------------------------------------------------------------

ooops... you're right I didn't check the value changed according the cpu is
under load or not !!
it probably was always at full speed ...

2009/4/14 Amit Kucheria <email address hidden>

> Hmm.. I don't see any changes to bogomips in my /proc/cpuinfo when I
> change the frequency from the frequency-applet
>
> Only my cpu MHz value changes.
>
> On Tue, Apr 14, 2009 at 10:34:08AM -0000, Jeremy Vies wrote:
> > I've got a core2duo e7300. It runs normally at 2.66GHz (10*266). I've
> just
> > changed FSB to 333.
> > I use Ubuntu out of box settings, so I think it's ondemand.
> >
> >
> > 2009/4/14 Amit Kucheria <email address hidden>
> >
> > > Can you provide details of your processor, your cpufreq driver and
> > > governor?
> > >
> > > On Tue, Apr 14, 2009 at 09:27:01AM -0000, Jeremy Vies wrote:
> > > > Hi all,
> > > >
> > > > I've just tested this week-end with a Jaunty up-to-date. The
> frequency
> > > > scaling worked, it was only the value displayed by the kernel that is
> > > wrong.
> > > > In /proc/cpuinfo, I could read the stock value for cpu speed, whereas
> the
> > > > bogomips was changed !
> > > >
> > > > JV
> > > >
> > > > 2009/4/14 Amit Kucheria <email address hidden>
> > > >
> > > > > Testing with the latest pre-release of Jaunty 9.04 will also help
> us
> > > > > identify if this exists in the latest upcoming release. Refer to
> > > > > http://www.ubuntu.com/testing/jaunty/beta . Please let us know.
> > > > >
> > > > > ** Changed in: linux (Ubuntu)
> > > > > Status: Triaged => Incomplete
> > > > >
> > > > > --
> > > > > Cpu frequency scaling is limited to stock speeds
> > > > > https://bugs.launchpad.net/bugs/132403
> > > > > You received this bug notification because you are a direct
> subscriber
> > > > > of the bug.
> > > > >
> > > >
> > > >
> > > > --
> > > > Theory is where you know everything, but nothing works; practice is
> where
> > > > everything works, but nobody knows why. Here we combine theory with
> > > > practice; nothing works and nobody knows why !
> > > > A.Einstein
> > > >
> > > > --
> > > > Cpu frequency scaling is limited to stock speeds
> > > > https://bugs.launchpad.net/bugs/132403
> > > > You received this bug notification because you are a member of Ubuntu
> > > > Kernel Team, which is subscribed to linux-source-2.6.22 in ubuntu.
> > >
> > > --
> > > ----------------------------------------------------------------------
> > > Amit Kucheria, Kernel Engineer || <email address hidden>
> > > ----------------------------------------------------------------------
> > >
> > > --
> > > Cpu frequency scaling is limited to stock speeds
> > > https://bugs.launchpad.net/bugs/132403
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> >
> >
> > --
> > Theory is where you know everything, but nothing works; practice is where
> > everything works, but nobody knows why. Here we combine theory with
> > practice; nothing works and nobody knows why !
> > A.Einstein
> >
> > --
> > Cpu frequency scaling is limited to stock speeds
> > https://bugs.launchpad.net/bugs/132403
> > You received this bug notification because you are a member of Ubuntu
> > Kernel ...

"Does this mean that the BIOS upgrade fixed your problems?"

Yes, it does.

My working assumption (read: guess, based on observed behavior) is that the available steps are read through some BIOS calls, and when your CPU is newer than your BIOS, the data is incomplete and Speedstep can't therefore work.

Everything has worked "by the book" on that box after I updated the BIOS. Things run cooler and faster than before, and idling is *very* cool indeed.

BIOS upgrade fixed the problem. Marking as Invalid based on this.

I doubt that marking the whole bug as invalid is the way to go. A BIOS update might have solved PetriL's problem although he seems to be the only one because forums are full of people missing speedstep with overclocked Intel cpu's. My E6600 is well supported from my motherboard's BIOS and works overclocked with EIST/C1E under Windows, while Linux refuses to enable speedstep.

Also note that other bugs (e.g. #213119 or #175310) are marked as duplicate of this one and this bug is marked invalid now. I believe the problem still exists and lies within the upstream kernel as there was some discussion on LKML before (can't find it anymore, sorry) and kernel developers stated they don't care about overclocking so noone tried to fix it. Ubuntu on the other hand is a distribution with a huge base of desktop users and we do overclock our hardware sometimes.

this problem has not changed in karmic with 2.6.31 and 2.6.32 (mainline), and lucid with 2.6.32
i have to disable speedstep in the BIOS to enable the overclocked frequency.

on other kernels (phc for example) it's possible to unload the acpi-cpufreq module as a workaround - but the module is not modular (compiled in) with the the ubuntu kernels :(

i need to overclock to watch 1080p movies smoothly :(

Intel(R) Core(TM)2 Quad CPU Q9450
stock: 2.66GHz
overclocked to 3,2 GHz (FSB 400)
on Asus P5K with Intel P35/ICH9

It is highly likely the system is still overclocked, ubuntu is just reporting the wrong speed.

see bug 379873: https://bugs.launchpad.net/ubuntu/+bug/379873