Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

macbook pro won't go into standby (deep sleep)

Hello,


I have a mid 2012 Macbook pro (MD101) base specs (4GB memory, 500GB hard drive, etc running the latest version of Yosemite). Several weeks ago, I bought a Thunderbolt display, USB keyboard, and a wireless mouse. I've noticed that around the time I started using this setup (Not sure if it's exactly the same time), that my macbook pro no longer goes into standby mode after the default 70 or so minute of sleep. It goes into regular sleep mode where the information is saved to memory only (when the status light is pulsing), but never into the mode where it saves the information to disk. I've checked my system settings (below) In pmset, reset the SMC, NVRAM, disabled wake for bluetooth device, wake for network activity, deleted sleepimage file, etc. all to no avail. At first, I thought I had fixed the problem because I noticed that standby enabled was set to 0, but it still did not work even when I changed it back to 1.


I also noticed that when I went into terminal as I am typing this post to paste the settings under peset -g, that standby had been changed back to 0. Somehow it is changing itself. How is this possible?


This issue is not such a big problem when I am at home using my macbook pro connected to the thunderbolt display, but it will be a huge problem when I take my laptop to school in September.


How do I get my computer to go back to the normal setting of going into standby/hibernate after 70 minute of normal sleep?


Current settings:


Active Profiles:

Battery Power -1*

AC Power -1

Currently in use:

standbydelay 4200

standby 1

halfdim 1

sms 1

hibernatefile /var/vm/sleepimage

disksleep 10

sleep 20

autopoweroffdelay 14400

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 5

acwake 0

lidwake 1

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10.5)

Posted on Aug 29, 2015 5:47 PM

Reply
8 replies

Aug 31, 2015 9:16 PM in response to alex 757

that's not entirely what I was looking for. I see auto-power off as being something separate from standby/hibernate. When auto-power off is selected, the computer shuts down completely correct? I'm talking about standby/hibernate, which is like a deep-sleep where the contents of memory are written to the hard drive under the sleepimage file.


The latest update is that my macbook pro is now going into standby when it is not connected to the thunderbolt display after 70 minute of sleep as normal about 50% of the time. During other times however, it will sleep for 70 minutes, attempt to go into standby, but instead a kernel panic will occur, and it restarts altogether.


As far as when it is connected to the thunderbolt display, it is still just staying in normal sleep mode (with the status light glowing), but never going into standby. Maybe this is normal for when it is connected to thunderbolt?


How do I stop the kernel panic from occurring when the computer attempts to go from normal sleep to standby?

Aug 31, 2015 10:54 PM in response to alex 757

Actually, upon further investigation and reading the definition of "autopoweroff" setting, I think that is correct... let me try setting standby back to 0- which seems to be the default, allow it to autopoweroff after 14400 seconds (4 hours), and see if the kernel panics stop...


After reading the definition of Autopoweroff vs the definition of standby, it seems like they are exactly the same. what is the difference?

Sep 1, 2015 8:56 PM in response to alex 757

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

When you post the report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Sep 3, 2015 10:50 PM in response to Linc Davis

It looks like i was probably wrong. these incidents happened on battery power with the lid of the laptop closed- not while it was connected to the thunderbolt display. I just happened to be sitting nearby reading when both incidents occurred. The computer was asleep with the lid closed one second, and then the next thing I know, I heard it restart itself, and received an error message once I opened the lid up and logged back in to find out why it randomly restarted. I assumed that the cause was a kernel panic, but it seems to be a sleep-wake failure. I'm not sure what the difference is...

Sep 4, 2015 6:12 AM in response to alex 757

Step 1

Take all the applicable steps in this support article. That's the starting point for any further efforts to solve the problem. Please read the whole article carefully and don't skip any of the steps, including the ones under the heading Learn more. If you don't understand any of the steps, ask for guidance.

Wake failures can be caused by peripheral devices. Be sure to disconnect those, if applicable, as directed in the article.

Also note that if you replaced the internal hard drive with an SSD, or if you're starting up from an external SSD, then that device may be causing the problem. Check the SSD manufacturer's website for a firmware update. The only solution may be to reinstall the original drive or avoid sleep altogether.

Step 2

If you're running OS X 10.8.5 or earlier, from the menu bar select

 ▹ System Preferences... ▹ Accessibility

If the checkbox at the bottom marked

Enable access for assistive devices

is checked, uncheck it and test.

If you're running OS X 10.9 or later, select

 ▹ System Preferences... ▹ Security & Privacy ▹ Privacy ▹ Accessibility

If any applications are listed on the right and have a checked box next to them, uncheck all the boxes and test. You may first have to click the padlock icon in the lower left corner of the window and authenticate as an administrator to unlock the settings.

Step 3

Back up all data.

Triple-click the line below on this page to select it, then copy the text to the Clipboard by pressing the key combination command-C:

/var/vm

In the Finder, select

Go Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You may not see what you pasted because a line break is included. Press return.

A folder named "vm" should open. Inside it, there may be a file named "sleepimage". Move that file, and only that one, to the Trash, but don't empty yet. You'll be prompted for your password. Close the folder window.

Restart the computer and empty the Trash.

Step 4

In the Energy Saver pane of System Preferences, uncheck the box marked

Put hard disks to sleep when possible

Step 5

If the machine is bound to a network directory server (Open Directory, Active Directory, or LDAP), temporarily unbind it in the Users & Groups preference pane and test. You must by logged in as a local administrator to do this.

If you don't know what a network directory server is, this step doesn't apply to you.

Step 6

If you have replaced or added memory, test with only the original memory installed.

Step 7

If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.

*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

Step 8

This and the next step must be taken as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION Diagnostic and Usage Messages

In the search box in the window's toolbar, enter "powerd" (without the quotes.)

You may see one or more lines like this:

com.apple.message.signature: Platform Failure

or

com.apple.message.signature: Drivers Failure

If you do see that, and you did everything in the preceeding steps, then you're dealing with an internal hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Step 9

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that heading, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down.

You may see one or more reports with a name that begins with "Kernel" or "Sleep Wake Failure" followed by a date. Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

macbook pro won't go into standby (deep sleep)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.