Long time to sleep/shutdown/reboot on Mavericks

[kenia1234]

Hi all.
I own an ASUS laptop (N56VZ) with i7 Ivy Bridge (3630Q) CPU, Intel HD 4000 and OSX Mavericks (10.9.2) running almost flawlessly on my configuration.
Of course I do have a good power management, fixed via SSDT and AppleIntelCPUPowerManagement.kext (Not NullCPU) and I checked that my power management was actually working pretty well with P and C states generated by SSDT (not by Clover).
I have a weird problem though.
Even if the PC actually goes into stop mode, reboots and shuts down correctly, it takes much longer than it did on Mountain Lion (10.8.5).
In fact with Mountain Lion with the same configuration, sleep happened in 1-2 seconds, shutdown in 5-6 seconds and the same for reboot.
With OSX Mavericks, sleep happens in 25-30 seconds, shutdown in 35-40 seconds and the same for reboot.
Why do I have such a long sleep/shutdown/reboot time in your opinion?
And what should I do to fix it (since power management is already working very well)??

 

[RehabMan]

Hi all.
I own an ASUS laptop (N56VZ) with i7 Ivy Bridge (3630Q) CPU, Intel HD 4000 and OSX Mavericks (10.9.2) running almost flawlessly on my configuration.
Of course I do have a good power management, fixed via SSDT and AppleIntelCPUPowerManagement.kext (Not NullCPU) and I checked that my power management was actually working pretty well with P and C states generated by SSDT (not by Clover).
I have a weird problem though.
Even if the PC actually goes into stop mode, reboots and shuts down correctly, it takes much longer than it did on Mountain Lion (10.8.5).
In fact with Mountain Lion with the same configuration, sleep happened in 1-2 seconds, shutdown in 5-6 seconds and the same for reboot.
With OSX Mavericks, sleep happens in 25-30 seconds, shutdown in 35-40 seconds and the same for reboot.
Why do I have such a long sleep/shutdown/reboot time in your opinion?
And what should I do to fix it (since power management is already working very well)??

The sleep part is normal. There is an intentional ~20 sec delay for sleep in Mavericks (on real Macs too).

Not so sure about the other...

If you want me to look it over, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

 

[kenia1234]

The sleep part is normal. There is an intentional ~20 sec delay for sleep in Mavericks (on real Macs too).

Not so sure about the other...

If you want me to look it over, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

Are you sure that it's normal? I've seen many recent macbook (with the same hardware as mine) with instant sleep time.
And why should Apple choose to make sleep slower. I think it's non sense.
However I attached my IOReg.
Everything else is working perfectly on my machine (Except for nVidia card and VGA/HDMI ports), and it is very quick, snappy and blazing fast in every operations.
Thank you for your answer.

 

[RehabMan]

Are you sure that it's normal? I've seen many recent macbook (with the same hardware as mine) with instant sleep time.

How did you test/verify? There is no outward indication of sleep on my MacBookAir. When you order sleep, you can't tell the difference between sleeping and waiting to sleep. The only way to tell is to look at system.log after.

I haven't tested since 10.9 first came out. Not sure if there has been any change on my MacBookAir since then. I guess it would be something to look into... My guess is nothing has changed.

And why should Apple choose to make sleep slower. I think it's non sense.

I'm not sure what their reasoning is.

However I attached my IOReg.
Everything else is working perfectly on my machine (Except for nVidia card and VGA/HDMI ports), and it is very quick, snappy and blazing fast in every operations.
Thank you for your answer.

You might want to try custom SSDT and dropping OEM SSDTs. Sometimes requires careful analysis of OEM SSDTs...

You could also try booting verbose. When you boot verbose, you also get verbose shutdown/restart.

Try to eliminate third party system software, such as Boom, LittleSnitch... just a couple that jumped out at me.

 

[kenia1234]

How did you test/verify? There is no outward indication of sleep on my MacBookAir. When you order sleep, you can't tell the difference between sleeping and waiting to sleep. The only way to tell is to look at system.log after.

I haven't tested since 10.9 first came out. Not sure if there has been any change on my MacBookAir since then. I guess it would be something to look into... My guess is nothing has changed.

Because when I press the power button of the mac it goes to sleep, but I press it again just 2 seconds later and it opens up again.
So I guess that sleep takes almost 2 seconds on some recent real macbook.

I'm not sure what their reasoning is.

Yup, it would be absolutely non-sense.

You might want to try custom SSDT and dropping OEM SSDTs. Sometimes requires careful analysis of OEM SSDTs...

You could also try booting verbose. When you boot verbose, you also get verbose shutdown/restart.

Try to eliminate third party system software, such as Boom, LittleSnitch... just a couple that jumped out at me.

I already have custom SSDT and dropped C-P states of Clover.
Thanks for the suggestions, but apart from shutdown/reboots, the most annoying thing for me is sleep.
It was instant of Mountain Lion! :/

 

[RehabMan]

Because when I press the power button of the mac it goes to sleep, but I press it again just 2 seconds later and it opens up again.
So I guess that sleep takes almost 2 seconds on some recent real macbook.



Yup, it would be absolutely non-sense.

You did not read what I wrote... There is no outward indication of sleep (no blinking led). You cannot tell the difference just looking at it. You must analyze system.log. Because I hadn't done it in a while, I tested again on my MacBookAir6,2. The result is the same... sleep commences about ~18 seconds after the request via Apple->Sleep.

Here is my annotated log:

**** Marker placed to mark when I’m about to select Apple->Sleep
 Marker - May 3, 2014, 4:15:43 PM

**** Apple->Sleep selected 3 sec later at 15:46
May  3 16:15:46 MacBookAir-ML.local WindowServer[93]: _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
May  3 16:15:46 MacBookAir-ML.local loginwindow[65]: find_shared_window: WID -1
May  3 16:15:46 MacBookAir-ML.local loginwindow[65]: CGSGetWindowTags: Invalid window 0xffffffff
May  3 16:15:46 MacBookAir-ML.local loginwindow[65]: find_shared_window: WID -1
May  3 16:15:46 MacBookAir-ML.local loginwindow[65]: CGSSetWindowTags: Invalid window 0xffffffff
May  3 16:15:46 MacBookAir-ML kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
May  3 16:15:46 MacBookAir-ML.local WindowServer[93]: device_generate_desktop_screenshot: authw 0x7fb1f354c500(2000), shield 0x7fb1f3448530(2001)
May  3 16:15:46 MacBookAir-ML.local WindowServer[93]: device_generate_lock_screen_screenshot: authw 0x7fb1f354c500(2000), shield 0x7fb1f3448530(2001)
May  3 16:15:46 MacBookAir-ML kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

**** Long pause before anything is started again, but no sleep yet 15:46 to 16:04, or ~18 sec
May  3 16:16:04 MacBookAir-ML.local loginwindow[65]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

**** At 16:08, system starts to really get sleep going, now T plus ~22 sec
May  3 16:16:08 MacBookAir-ML kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000280
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 274.734083: AirPort_Brcm43xx::powerChange: System Sleep 
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 274.734091: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.
May  3 16:16:08 MacBookAir-ML kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
May  3 16:16:08 MacBookAir-ML kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf400 ****
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407290: scanparams:
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407294:   flags 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407296:   active_time 0, passive_time 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407298:   scan_start_delay 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407300:   scan_cycle_idle_rest_time 0, scan_cycle_idle_rest_time_multiplier 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407303:   max_scan_cycles 0, max_rest_time 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407305: Scan Channels (0): None
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407307: SSID (0): None
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407309: SSID count = 0
May  3 16:16:08 MacBookAir-ML kernel[0]: ARPT: 275.407311: wl0: leaveModulePoweredForOffloads: Wi-Fi will stay on.
May  3 16:16:08 MacBookAir-ML kernel[0]: Bluetooth -- LE is supported - Disable LE meta event
May  3 16:16:08 MacBookAir-ML kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 1519 us
May  3 16:16:08 MacBookAir-ML kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
May  3 16:16:08 MacBookAir-ML kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf400 ****
May  3 16:16:08 MacBookAir-ML kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
May  3 16:16:09 MacBookAir-ML kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

**** Last log before sleep at 16:09, now T plus ~23
May  3 16:16:09 MacBookAir-ML kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 2

**** System actually went to sleep, and I woke at 16:55
May  3 16:16:55 MacBookAir-ML kernel[0]: Wake reason: SPIT (User)

I already have custom SSDT and dropped C-P states of Clover.

You might want to check it. It didn't look that way when I looked at your ioreg.

Thanks for the suggestions, but apart from shutdown/reboots, the most annoying thing for me is sleep.
It was instant of Mountain Lion! :/

Not a hackintosh issue. It is working as Apple intends.

 

[kenia1234]

You did not read what I wrote... There is no outward indication of sleep (no blinking led). You cannot tell the difference just looking at it. You must analyze system.log. Because I hadn't done it in a while, I tested again on my MacBookAir6,2. The result is the same... sleep commences about ~18 seconds after the request via Apple->Sleep.

Here is my annotated log:
Not a hackintosh issue. It is working as Apple intends.

I know that there is no indicator, but if I press the power button and my laptop goes to sleep, I cannot wake it up until it goes to sleep completely. In the Macbook Pro that I tried, instead, I could press the power button right after I pressed it to make it sleep and it wakes up immediately. :/ However if it isn't a hackitnosh issue it's kinda weird.

You might want to check it. It didn't look that way when I looked at your ioreg.

What do you mean? Where am I wrong in your opinion?

Thanks for the quick answers!!

 

[RehabMan]

I know that there is no indicator, but if I press the power button and my laptop goes to sleep, I cannot wake it up until it goes to sleep completely.

Then something is not working correct with sleep or perhaps display brightness, or perhaps the power button... Does the same happen when you use Apple->Sleep, or is this specific to your power button?

Are you certain the laptop actually made it to sleep? Because sleep does not happen until after ~20 sec. The time between sleep request and sleep, just the display is off. If you have issues with your display coming back you'll need to figure out if that is happening and why. Use an external monitor to connect to the machine or try to connect from another machine via Screen Sharing and VNC.

What do you mean? Where am I wrong in your opinion?

There is more than one SSDT in your ioreg. I meant that you should check that all the ones in addition to the one you generated are intended.

 

[kenia1234]

Then something is not working correct with sleep or perhaps display brightness, or perhaps the power button... Does the same happen when you use Apple->Sleep, or is this specific to your power button?

Are you certain the laptop actually made it to sleep? Because sleep does not happen until after ~20 sec. The time between sleep request and sleep, just the display is off. If you have issues with your display coming back you'll need to figure out if that is happening and why. Use an external monitor to connect to the machine or try to connect from another machine via Screen Sharing and VNC.



There is more than one SSDT in your ioreg. I meant that you should check that all the ones in addition to the one you generated are intended.

Thanks Rehabman!!
You solved my problem!!
I made some tries with Screen Sharing and you are absolutely right!
When I click on Stop, the computer actually turn off the screen but doesn't go to sleep, but if I click another button while it is going to sleep, it resumes instantly.
I mean that the sleep process is actually very fast, it just happens with a delay of 30 seconds.
As regards shutdown and reboot time, I use many third-part apps, so I guess it is that!
Thank you very much again, this thread can be closed!

 

[RehabMan]

Thanks Rehabman!!
You solved my problem!!
I made some tries with Screen Sharing and you are absolutely right!
When I click on Stop, the computer actually turn off the screen but doesn't go to sleep, but if I click another button while it is going to sleep, it resumes instantly.
I mean that the sleep process is actually very fast, it just happens with a delay of 30 seconds.
As regards shutdown and reboot time, I use many third-part apps, so I guess it is that!
Thank you very much again, this thread can be closed!

So I take it you found a solution or found that an app you installed was causing the issue? Please elaborate on the solution.