pmset produces incorrect error message

Originator:jollysupport
Number:rdar://728970 Date Originated:10/9/09
Status:open Resolved:
Product:MacOS X Product Version:10.6.1
Classification:Other Bug Reproducible:always
 
09-Oct-2009 11:00 AM Patrick Stein:
Summary: When using pmset to set the hibernate mode with a disksleep 0 and system sleep time you get an erromessage even though it's not really an error.

Steps to reproduce set Systemsleep to 10 , disksleep to 0 and then use pmset hibernatemode 0 :

#pmset -g                                                                                                                                   

Active Profiles:
Battery Power		-1
AC Power		-1*
Currently in use:
 womp		1
 lidwake	1
 halfdim	1
 sms		1
 hibernatefile	/var/vm/sleepimage
 disksleep	0
 sleep		57
 hibernatemode	0
 ttyskeepawake	1
 displaysleep	57
 acwake		0
 autorestart	0


#sudo pmset hibernatemode 0                                                                                                                                                   
Warning: Idle sleep timings for "AC Power" may not behave as expected.
- Disk sleep should be non-zero whenever system sleep is non-zero.


The code that is responsible for that is http://opensource.apple.com/source/PowerManagement/PowerManagement-31/pmset/pmset.c?f=text

line 660ff:

    if(sleep_time != 0)
    {
        if(dim_time > sleep_time || dim_time == 0) ret |= kInconsistentDisplaySetting;
    
        if(disk_time == 0) ret |= kInconsistentDiskSetting;
    }


I don't see it as inconsistency for the pmset hibernate mode there or for the disk to never spin down until system sleep.

Expected behaviour: no error message.



Best Regards - Patrick Stein 

 ---
author of: ScreenRecycler, JollysFastVNC, SmartSleep, SmartSokoban and more.




Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!