-xen kernel does not support cpufreq

Bug #137596 reported by Martin Emrich
22
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Low
Ubuntu Kernel Server Team

Bug Description

Binary package hint: linux-source-2.6.22

Maybe this is intentional, but the current linux-image-2.6.22-10-xen does not contain
support for cpufreq/speedstep. So my CPU (P-M 1,7GHz) is locked at 667MHz instead of 1,7 GHz
(/proc/cpuinfo says so, and it feels very slow, too).

If xen supports setting the CPU frequency from Dom0, please enable cpufreq support in the -xen kernels.

Thanks

Martin

Revision history for this message
Marsu42 (marsu42) wrote :

This is a vital module for me (yes, I am running xen on my laptop, thank you, it's the fastest box I have...). Please fix it asap, w/o scaling it tends to overheats and crash.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Thanks for reporting. Could you please attach the information requested in https://wiki.ubuntu.com/KernelTeamBugPolicies ?

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-server
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Martin Emrich (emme) wrote :

Since then, 2.6.22-11 came out, now my CPU frequency is at 1.7 GHz, but still no cpufreq support. The modules are simply not there, they are not part of the kernel. So I don't know why the additional files are needed, but here they are, nevertheless.

Ciao

Martin

Revision history for this message
Marsu42 (marsu42) wrote :

...dmesg output attached as requested.

Revision history for this message
Marsu42 (marsu42) wrote :

...lspci output attached as requested.

Revision history for this message
Martin Emrich (emme) wrote :

I took a look at the Xen documentation and their website, it seems that Xen 3.0/3.1 do not support any cpu frequency scaling at all, it looks like they are currently working on it (maybe for Xen 3.2). So this it not really a bug, but rather a missing feature.

Ciao

Martin

Revision history for this message
feeling (feeling001) wrote :

Exactly same problem for me...

throtteling works, acpi looks ok. But, no cpufreq module and the cpu is locked to max frequency (energy loss ...)

Revision history for this message
Markus Kienast (elias1884) wrote :

confirm for gutsy

Revision history for this message
Hunter Allred (hunter-allred) wrote :

confirmed for gentoo as well. Furthermore, cpu freq scaling worked great on 2.6.20-xen-r6 :(

Revision history for this message
Martin Emrich (emme) wrote :

As I don't think Xen 3.2 will be backported to gutsy, I'd recommend to mark this "bug" as Invalid to keep the open bug count down.

Ciao

Martin

Revision history for this message
Emilio Scalise (emisca) wrote :

Hardy has Xen 3.2, but doesn't have cpufreq support on the Xen hypervisor nor the Xen dom0 kernel.

Redhat Enterprise 5.2 contains some patches to Xen and the Xen dom0 kernel that allow cpufreq on amd and intel cpus only if the dom0 has all the vcpu assigned.

The source package of the kernel that supports cpufreq are here:
http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/kernel-2.6.18-92.1.1.el5.src.rpm

Maybe someone could forward port those patches..

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.