ARB-82
Level 1 (20 points)
Mac OS X

Q: 2015 MBP Unexpected waking behaviour after sleep

I have an early 2015 MBP 13-inch and noticed the following:

 

What I expect:

After closing the lid, the MBP should wake up instantly when I open the lid again. No matter if only a few seconds have passed, or if many days have passed since closing the device: it should wake right away and have me continue where I left off.

 

What actually happens:

  1. When closing the lid the MBP will go to sleep
    1. When opening the lid within 1 hour the MBP will wake up right away in it’s original state (expected behaviour)
    2. When opening the lid after 1 hour the power button has to be used to wake up the device and it will boot up from scratch and restore it into it's old state.
  2. It does not matter if the device is connect to AC or running on battery

 

Please note:

  1. The hour might be a bit longer: it’s at least a ‘significant’ time. Opening the lid within the hour always results in a wake right away.
  2. This support article (https://support.apple.com/en-us/HT201635) states the following:
    1. OS X Mountain Lion v10.8.2 supplemental update 2.0 introduced a feature that lets your Mac enter safe sleep after four hours of being connected to AC power. This complies with European Energy Standards (ErP Lot6) and happens when there's no network activity and no activity from connected devices like external hard drives.
    2. However, it doesn't seem to be a Safe Wake, because it just looks and feels like a regular boot from scratch with 'reopen apps' selected. Also, as stated, it doesn't matter if the device is connected to AC or running on battery.

 

Question:

Is this normal behaviour? Is there any way this setting can be changed?

MacBook Pro with Retina display, OS X El Capitan (10.11.5), Early 2015 - 13 Inch

Posted on Jul 5, 2016 8:26 AM

Close
ARB-82

Q: 2015 MBP Unexpected waking behaviour after sleep

  • All replies
  • Helpful answers

  • by leroydouglas,

    leroydouglas leroydouglas Jul 5, 2016 10:00 AM in response to ARB-82
    Level 7 (23,789 points)
    Notebooks
    Jul 5, 2016 10:00 AM in response to ARB-82

    Try resetting the  SMC http://support.apple.com/kb/ht3964

  • by ARB-82,

    ARB-82 ARB-82 Jul 18, 2016 1:45 PM in response to leroydouglas
    Level 1 (20 points)
    Mac OS X
    Jul 18, 2016 1:45 PM in response to leroydouglas

    Unfortunately this has not resulted in any change. The mac just seems to be booting from scratch, as if it was shut down by the user. It tries to start applications again, but this of course is not the same as a wake from sleep. It should go back straight to were it left off.

     

    Are there any settings I can look into via the terminal? It seems like a software/configuration issue. Somehow it decides that after a few hours it should go into standby.

     

    I found this in the logs:

     

    18/07/16 18:21:08,000 kernel[0]: ARPT: 14329.797437: IOPMPowerSource Information: onSleep,  SleepType: Standby,  'ExternalConnected': No, 'TimeRemaining': 13310,

    18/07/16 18:21:08,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

    18/07/16 22:29:04,000 bootlog[0]: BOOT_TIME 1468873744 0

     

    The macbook seems to shut itself down at 18:21:08 to go into standby...

     

    And right after it boots again:

     

    18/07/16 22:29:05,000 kernel[0]: Sleep failure code 0x00000000 0x1f006c00

  • by ARB-82,

    ARB-82 ARB-82 Jul 19, 2016 12:10 AM in response to ARB-82
    Level 1 (20 points)
    Mac OS X
    Jul 19, 2016 12:10 AM in response to ARB-82

    After updating to OSX 10.11.6 the issue is still the same:

     

    Close the lid, the device goes to sleep:

    18/07/16 23:27:51,000 kernel[0]: ARPT: 743.155391: IOPMPowerSource Information: onSleep,  SleepType: Deep Idle,  'ExternalConnected': No, 'TimeRemaining': 1798,

     

    It then wakes up a few times, but crucially at 02:28:00 decides that it no longer needs to keep the device asleep, rather put it in standby mode which is basically the same as shutting the device down.

     

    19/07/16 00:36:32,000 kernel[0]: Previous sleep cause: 5

    19/07/16 00:36:32,000 kernel[0]: ARPT: 745.583830: IOPMPowerSource Information: onWake,  SleepType: Deep Idle,  'ExternalConnected': No, 'TimeRemaining': 12339,

    19/07/16 00:37:04,000 kernel[0]: ARPT: 777.534184: AirPort_Brcm43xx::powerChange: System Sleep

    19/07/16 00:37:04,000 kernel[0]: ARPT: 777.534213: IOPMPowerSource Information: onSleep,  SleepType: Deep Idle,  'ExternalConnected': No, 'TimeRemaining': 12339,

    19/07/16 02:27:53,000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)

    19/07/16 02:27:53,000 kernel[0]: Previous sleep cause: 5

    19/07/16 02:27:53,000 kernel[0]: ARPT: 779.859883: IOPMPowerSource Information: onWake,  SleepType: Deep Idle,  'ExternalConnected': No, 'TimeRemaining': 11908,

    19/07/16 02:28:00,000 kernel[0]: ARPT: 786.792422: AirPort_Brcm43xx::powerChange: System Sleep

    19/07/16 02:28:00,000 kernel[0]: ARPT: 786.792452: IOPMPowerSource Information: onSleep,  SleepType: Standby,  'ExternalConnected': No, 'TimeRemaining': 11908,

    19/07/16 08:47:32,000 kernel[0]: ACPI: sleep states S0 S3 S4 S5

    19/07/16 08:47:32,000 kernel[0]: Sleep failure code 0x00000000 0x1f006c00

  • by ARB-82,

    ARB-82 ARB-82 Jul 19, 2016 9:57 PM in response to ARB-82
    Level 1 (20 points)
    Mac OS X
    Jul 19, 2016 9:57 PM in response to ARB-82

    It seems I have found an answer. In power management settings this option was enabled:

     

    DestroyFVKeyOnStandby: 1

     

    This option does exactly what is says: it destroys the FileVault Key on standby. After disabling the option, the MBP behaves as expected.

     

    - Check your current settings: "pmset -g"

    - Disable the option with: "sudo pmset -a DestroyFVKeyOnStandby 0"

     

    Please note that this option will have an impact on security, so please use caution.