MacBook Pro always hibernates

The same here since the last update.

It seems to wake fine if I sleep it then immediately wake it, but if I leave it asleep for a while, it wakes from hibernation. I wonder if this is just new logic, where it saves power for long sleeps by going into hibernation if it's been asleep for a few hours?

I'm having the same issue with my 13" MBP that's a few weeks old. Always hibernates on AC power if left for more than a few hours, but doesn't hibernate when on battery power. It's pretty **** annoying.

https://discussions.apple.com/thread/4555245

My original post is here incase someone finds an answer.

Thanks for the link to the other thread. For the record, I have a mid-2012 15" non-Retina MBP.

Also, I should also mention this only happens to me SOMETIMES, and I haven't been able to pin down when it does and when it doesn't..

Thanks for this post. I thought maybe it was just something wrong with my machine. I often leave my machine closed and plugged in over night, and it always awakes from hibernation the next morning, but does NOT do this if not plugged in. That is backwards in my view.

It also has that annoying problem of waking from sleep if you disconnect the power connection while sleeping. Not sure why that needs to wake the machine.

Hopefully Apple will post a fix in the next release.

Runing a MBP 2.9 Ghz Intel Core i7 (Mid 2012) with Mt Lion 10.8.2 (12C3012)

I have been experiencing this problem as well with my MacBook Pro (15-inch, Mid 2012) since a recent update (not sure what it was, but one of those updates where it needs to be plugged in, not just a usual OS update).

Yesterday I tried completely disabling hibernation mode (sudo pmset -a hibernatemode 0) and this morning it sill took over 2 minutes to “wake up”.

Symptoms I have noted:

(1) This only happens if plugged into power source (it has never had a problem waking up when not plugged into a power source)

(2) this happens when the computer has been charging for a “while” (more than an hour, but I have not found the exact amount of time that needs to pass).

(3) This happens whether the battery had a charge or not when I plugged it in (meaning even if the battery has half a load when I plug it in this happens)

(4) Sometimes the computer is obviously resuming from a hibernation instead of a simple sleep (evident from the grayed screen and progress bars as it loads the RAM image from the HD) but a lot of the times the screen is just black for a while and then once the image appears it still takes forever (like 120 000 milliseconds or so) before the computer actually works.

My next test is to open the lid before unplugging the power cable to see if this still happens.

Ok. I think I have been to disable this new "feature".

looking through my logs i see this:

2/21/13 7:39:09.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

2/21/13 11:38:54.000 AM kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)

....

2/21/13 11:39:13.000 AM kernel[0]: hibernate image major 1, minor 0, blocksize 512, pollers 5

...

2/21/13 7:30:30.000 PM kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff8093b50000, 0xffffff8093b70000

hummm. exactly four hours after i closed the lid, the device wakes itself up and hibernates.

searching google I find this thread that answers some questions:

http://apple.stackexchange.com/questions/72889/mountain-lion-aggressively-hibernates

this is what appears to be the solution:

sudo pmset -a autopoweroff 0

I just opened the lid after the laptop had been charging since 07:30 this morning and... bliss. I am typing this without having to have waited 120 000 milliseconds for my computer to respond.

This is due to the installation of DL1609 update. It has some issues, one of which is to hibernate afte 4 hours of sleep but only when plugged in. When on battery, it doens't sleep. It's buggy, Apple knows about it, they may not fix it because they say it's expected. Call AppleCare and complain please. I have several posts/threads on this matter if you wish to search and find them.

Lol, get the "caffeine" app from the app store. It really helps.

Ahhh. Update DL1609, aka "MacBook Air and MacBook Pro Update 2.0" which has the incredibly verbose and detailed description "This update includes graphics performance and reliability enhancements and improves compatibility with some USB devices."

What a pity that the days of installing Apple updates without even a second thought are gone. This is the first time I have had ever had to "work for my mac"[1] instead of it just working. From here on out I will being installing the updates when I know they fix a problem that I am actually experiencing, not just some vague promise of "realiabilty enhancements" which has been entirely the opposite.

-andrew

[1] Instead of just using my computer for productive purposes, having to spend my CPU cycles getting it to work...

> this is what appears to be the solution:

> sudo pmset -a autopoweroff 0

So, what side effects are there of this change? I would suspect that this also prevent it from hibernating on battery, when it should. Have you tested that?

>Lol, get the "caffeine" app from the app store. It really helps.

Uh, that controls sleep, or actually, preventing it from sleeping, and this is a problem with hibernate AFTER sleeping, while on power, which is a very different problem. You actually close your computer to put it to sleep (yes, we want it to sleep) but we do not want it to hibernate 4 hours later. Keeping it awake with the lid closed is not the right solution IMO.

Or perhaps I simply am not understanding how to use that app to solve this issue. Can you please explain how you think it helps with this problem? Thanks.

orubin wrote:

[quote]

this is what appears to be the solution:

sudo pmset -a autopoweroff 0

[/quote]

So, what side effects are there of this change? I would suspect that this also prevent it from hibernating on battery, when it should. Have you tested that?

That's just it, with this update installed, it doesn't hibernate when on battery no matter how long you wait. That's the bug that Apple needs to fix. Before DL1609 (the patch in question), if you enabled Standby with pmset, the laptop would hibernate after 4200 seconds while sleeping on battery but not when it's plugged in. Now, since that update, even with both autopoweroff and standby enabed/set to 1, the laptop hibernates after 14400 seconds of sleeping while on AC power, but won't hibernate after 4200 or 14400 seconds while on battery and not plugged in. See the issue? Ya, Apple screwed up and they're too stupid to notice it.

The negative side affect to the system not hibernating is that you end up eating more of the battery up since sleep takes more power to maintain the image within RAM as opposed to writing it to the hard drive and powering off the logic board. Because of this, you end up putting more charge cycles on the battery. The European countries complained to Apple about their batteries failing too early in the lifespan of their laptops, so Apple had to come up with a soluton to minimize the charge cycles and improve power management. They came up with the idea to hibernate the system after a certain amount of sleep, which is a fine idea, but they botched the implementation and mis-coded the OS to do it when it's plugged into power only. Well, along with the changes this patch introduced, and because these settings are enabled, when you plug and unplug the laptop from power (even when the screen is closed), the laptop wakes up from its current state (hibernation or sleep). So, since hibernate (which saves battery) only works when it's plugged in and the laptop wakes up (to change pmset modes) and goes back to sleep when you unplug it, you're still losing battery power because it won't hibernate on battery. lol Apple engineers are brain-dead. 😢

Yep, I get what was wrong, thanks for restating.

Just to be sure I am clear on your reasoning: Because it does not hibernate on battery anyway, might as well turn off the setting for power too, and the result is to fix it for power (no more hibernating while plugged in), and has "no effect" on battery because it was broken anyway? I suspect if they offer a fix (wait, Apple has not admited to the problem, so that may be a while), we would want to set this system variable back to 1?

Cheers