Red Hat Bugzilla – Bug 808508
Power Management fails for 3.3.x on Toshiba Tecra M7
Last modified: 2012-10-23 20:06:37 EDT
Description of problem:
When booting into kernel version 3.3.x the fan comes on at full speed an remains on at full speed.
Version-Release number of selected component (if applicable): 3.3.x
On the Toshiba Tecra M7, boot into Fedora using and version of the kernel in the 3.3 series.
Steps to Reproduce:
1.Install kernel 3.3.x via yum update
2.Restart computer and ensure kernel is selected in grub
3.Boot into Fedora
Fan comes on at full speed and continues indefinitely.
Fan comes on at low speed, only speeding up when the system is under a heavy load.
Booting into the 3.2.10 kernel via the grub menu produces the aforementioned "Expected results."
The latest kernel update in the fedora repository as of Sun Apr 1 does not fix the problem
The latest kernel update in the Fedora repository as of Sun Apr 8 does not fix the problem.
The latest kernel update in the Fedora repository as of Sat Apr 21 does not fix the problem.
The latest kernel as of May 23, 2012, at 21:08 CST, which is version 3.3.6-3, does not fix the problem.
This problem also applies to Fedora 17.
Created attachment 587867 [details]
The output of the lspci command
Is this still being seen with the 3.4 or 3.5 kernels in F16/F17? If so, could you please attach the output of dmesg and lsmod after a fresh boot?
# 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
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
I updated and everything seems to be fixed. Thanks.