Description of problem: I have found 2 bugs, which I suspect are closely related, hence reporting them both here. After hiberhate/restore cycle, the "pwm1_enable" value is *not* restored, it assumes value of 0 (disable fan management), even though the value before hibernate was 2 (automatic fan management). Worse still, when I manually execute "echo 2 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable", the automatic fan management kicks in, reduces my fan speed to minimum (pwm1 value goes down from 100 to 2), but then it stays at that value, regardless of the temperature of the video card! In normal circumstances, the pwm1 value hovers between 22-28 and the card temperature stays between 50-55 degrees, but after restore from hibernate the automatic management is not working, since it keeps my pwm1 value at 2, causing my card temperature to rise rapidly. THIS CAN CAUSE MY VIDEO CARD TO BURN OUT! The only solution to this is to deactivate automatic fan management: force a value of 1 to pwm1_enable and then set pwm1 to a safe value - something like 40 and also do that in /usr/lib64/pm-utils/sleep.d/ so that these values are assumed after my PC comes back from hibernate. Version-Release number of selected component (if applicable): kernel 2.9.6-200 How reproducible: Always, provided hibernate/restore is executed Steps to Reproduce: 1. Enable automatic fan management with "echo 2 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable" 2. Hibernate and then Restore 3. check the values with "cat > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable" and "cat > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1" - they should be 0 and 100 respectively, which is wrong since I had automatic fan management active before hibernate. 4. Set automatic fan management with "echo 2 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable" and watch your video card burn! Actual results: /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable is initially 0, despite being 2 before hibernate. When I manually execute "echo 2 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable" to enable automatic fan management, that is set (I get the "nouveau [ PTHERM][0000:01:00.0] fan management: automatic" message in my kernel logs), /sys/class/drm/card0/device/hwmon/hwmon0/pwm1 goes down to 2 and stays there regardless what the current temperature of my card is. In order to prevent my video card from burning out, I have to enable manual fan management with "echo 1 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable" and then set my fan to a safe value, something like "echo 40 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1". Expected results: Automatic fan management to be activated and work properly after hibernate/restore cycle Additional info:
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.