Can not adjust CPU frequency

Hi,

Thanks for taking the time to report this bug. Just one more piece of info that might be useful for debugging this issue (since it does seem to be specific to your CPU or system at the moment) is the contents of the following files after running cpufreq-selector:

/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Thanks,

/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:
800000

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:
conservative ondemand userspace powersave performance

/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:
performance

Thanks for providing the info. I would say this is definitely a bug then. I'd lean towards medium importance since it's stopping you from getting all your CPU cycles (apparently). That's assuming the content of cpuinfo_cur_freq isn't false somehow.

Marking as Medium per brendand's request.

The system is generally slower than before. It the content of cpuinfo_cur_freq seems to be correct.

For me, it sounds like:
Even the driver is broken or cpufreq-selector do nothing (security policies conflict or bad configuration?).

It's possible this is a duplicate of Bug #706089 which I reported earlier.

A test to check if this is the same case would be to use an older kernel, up to the exact version 2.6.32-24 because in my case frequency scaling works normally that way, but not with later kernels! I guess it is the same problem since the reporter says it works fine with Lucid.

If you have Lucid installed on your machine, could you try booting kernels older and newer than the above version to check this?

I don't have problems frequency scalling at Lucid's default kernel (2.6.32.X). There it works perfectly (via liveCD).
Linux 2.6.35.X (which is installed default by Maverick) doesn't work due of ACPI problems.

Therefore this bug is not a duplicate of #706089.

PS: At whose who affects this bug, too: Please post informations about the CPU and the content of the files from post 2 (see above).

Please don't mark this as a duplicate unless you're sure your hardware is the same.

@Brendan Donegan: couldn't it still be that both problems have the same cause, although the hardware is different? The symptoms seem exactly the same (lowest frequency, same cpu /sys files contents etc.)...

@firefuel: I would be very interested if you could check if Lucid (not only Maverick and Natty) with kernels (2.6.32-X), versions from 2.6.32-25 and above, are those capable of scaling your CPU's frequency? Perhaps you could install it to a usb-drive if you have some time to spare...

If you get the same results that would point to the direction of problem being in the kernel, and one that was introduced in the 2.6.32-25 version...

A.Kromic,

It could well be, but with (potential) kernel bugs the best practice is to never duplicate, as the problem could be architecture specific or caused by certain drivers. Best to let them be investigated individually.

It's different with user space bugs as the code will be the same no matter what hardware it's running on, so a lot easier to say 'same symptom, same fix'

Fix from bug #706089 works, marked as duplicate.

Nicolai_J., this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Confirmed with Kubuntu 13.4 on a Lenovo B590

Miroslav Milanovic, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]