Hide Forgot
Created attachment 530359 [details] The output of lspci Description of problem: In Fedora 16, at least one of the fans in my laptop is constantly running in a rather high speed, even when idle for a long while. Temperatures seem higher than desirable (32.7 78.0 degrees C). I'm seeing the same issue in Ubuntu 11.10, with about the same kernel version. When using Ubuntu, the computer would sometimes just power off, probably due to overheating. I've seen temperatures above 120 degrees C. Version-Release number of selected component (if applicable): Running kernel 3.1.0-1.fc16.x86_64. How reproducible: Everytime I start the computer.
Do you still see this with the 3.2.7 kernel (or newer)? If so, is there anything running an inordinate amount of time in powertop or top output?
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Same here with F17 beta, kernel 3.3.4-1. AMD/ATI combination though. If this problem is a general one, this bug might be a duplicate of #736063.
I have Fedora17 beta installed on a Netbook with 1 gig of memory. The fan is running again at high speed after a reboot to kernel vmlinuz-3.3.4-5.fc17.i686 It takes about 10 minutes for things to settle down to where the fan is returned to slow mode. Is there some monitoring, aside from the top command that is indicative of power / cpu consumption?
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.