Bug 495308
| Summary: | CPU Frequency gets stuck at maximum speed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Francisco Moraes <francisco.moraes> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | itamar, kernel-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-18 09:14:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: CPU Frequency scaling gets stuck at highest speed spontaneously. After the computer is running for a while, it goes into max speed and it cannot be changed. A suspend/resume solves the problem for a few hours but the problem reoccurs. Version-Release number of selected component (if applicable): 2.6.27.21-170.2.56.fc10.i686 How reproducible: This is happening on an IBM ThinkPad T60p 2007-AD1 computer running FC10 and the lastest updates. Steps to Reproduce: 1. Normal usage, including watching videos on hulu 2. CPU frequency gets stuck on max as noticed by temperature increase of CPU 3. cpufreq-set no longer works Actual results: Output from cpufreq-info: cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpufreq.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 1000 MHz - 2.17 GHz available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: ondemand, userspace, performance current policy: frequency should be within 1000 MHz and 1000 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.17 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: 1000 MHz - 2.17 GHz available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: ondemand, userspace, performance current policy: frequency should be within 1000 MHz and 1000 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.17 GHz (asserted by call to hardware). Expected results: CPU frequency scaling doesn't get stuck Additional info: