Hide Forgot
Created attachment 551565 [details] lspci output Description of problem: After resuming from suspend, fans run at full speed. Version-Release number of selected component (if applicable): How reproducible: Seemingly random, but roughly 4/5 resumes will result in this behavior. Steps to Reproduce: 1.Suspend system 2.Resume Actual results: Fan runs at full speed after resuming, everything else seems to work normally. Expected results: Fan should run at normal speed (or not at all). Additional info: 1. The fans seem to randomly spin down again after a longer period of time (5-10 minutes). This seems to be extremely rare though, I can recall it happening once or twice. 2. This is similar in spirit to the following bug, however, this seems to be OS-related, not BIOS-bound, since I am dual booting Windows XP Professional, and to my memory never experienced the bug there: https://bugzilla.redhat.com/show_bug.cgi?id=243008 3. IMPORTANT: Plugging or unplugging the power cable causes the fans to go down to normal speed again. lspci output in attachment.
My smolt profile: http://www.smolts.org/show?uuid=pub_37b46c83-d6c8-497a-8a72-88acd0eceb84+
Created attachment 552362 [details] lspci -vv output
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Bug is still reproducible using kernel-3.3.0-4.fc16
# 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.
My apologies for the late response. I am unable to replicate the bug as of kernel 3.6, it looks like it has been resolved. You may permanently close this bug if you wish.