Bug 433216 - CPU fan runs at full speed after S3 resume and can no longer be controlled
Summary: CPU fan runs at full speed after S3 resume and can no longer be controlled
Keywords:
Status: CLOSED DUPLICATE of bug 243008
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-17 17:50 UTC by Dennis Wagelaar
Modified: 2009-06-10 08:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-10 08:31:08 UTC


Attachments (Terms of Use)

Description Dennis Wagelaar 2008-02-17 17:50:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl; rv:1.8.1.12) Gecko/20080208 Fedora/2.0.0.12-1.fc8 Firefox/2.0.0.12

Description of problem:
Normally, the BIOS controls my CPU fan speed to stay somewhere around 900 RPM. I found that it can also be controlled by lm_sensors' fancontrol script (lm_sensors-2.10.5-1.fc8). After I resume from S3 sleep mode, however, the fan runs at full speed (ca. 1800 RPM) and can no longer be controlled by fancontrol. Note that the CPU fan normally runs at full speed on power-up, after which it is slowly throttled down by the BIOS.

Version-Release number of selected component (if applicable):
kernel-2.6.23.15-137.fc8

How reproducible:
Always


Steps to Reproduce:
1. Enter S3 sleep mode
2. Resume
3.

Actual Results:
Fan runs at max speed and can no longer be controlled (noise!!)

Expected Results:
Fan returns to low RPM and/or can be controlled by fancontrol

Additional info:
Mainboard: MSI G965MDH (http://global.msi.com.tw/index.php?func=proddesc&prod_no=1122&maincat_no=1)
CPU: Intel Core2 Duo E6300

Comment 1 Bug Zapper 2008-11-26 09:50:52 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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

Comment 2 Bug Zapper 2009-01-09 06:00:14 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.

Comment 3 Dennis Wagelaar 2009-01-13 07:04:55 UTC
Bug still occurs in Fedora 9 (kernel-2.6.27.9-73.fc9.x86_64).

Comment 4 Bug Zapper 2009-06-09 23:34:23 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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

Comment 5 Christopher Brown 2009-06-10 08:31:08 UTC

*** This bug has been marked as a duplicate of bug 243008 ***


Note You need to log in before you can comment on or make changes to this bug.