Sleep Wake Failure on new MBP 2016

Discussion in 'MacBook Pro' started by Calby, Feb 12, 2017.

  1. Calby, Feb 12, 2017
    Last edited: Feb 12, 2017

    Calby macrumors 6502

    Calby

    Joined:
    Dec 30, 2015
    Location:
    Sweden, Gävle
    #1
    Hi,
    First some spec:
    MacBook Pro 2016 13" nonTB
    Apple's USB-C to HDMI/USB-C/USB-A adapter
    macOS 10.12.3
    I use the MBP in clamshell mode (the MBP closed) when its attached to the screen.

    I did not have any kind of issue, almost anyway besides one kernel panic for like 4 weeks ago it was because of Bluetooth and I did uninstall the Logitech software and the issue was gone.

    Yesterday I did purchase a 24" screen and a external keyboard I did also buy Apples USB-C adapter for HDMI/USB-A/USB-C.
    When I did attach it it aoutmatlic did pop up something from the system that wanted me to install it to have better experience with it, don't remember the name.
    But later on when I did try to wake it up, It has been sleeping for like 3h it wakes up and says that it has rebooted due to a error.
    And in Console I can find "Sleep Wake Failure_2017-02-12-191335_Robins-MacBook-Pro.diag"

    Why's this? Is it some kind of hardware issue on my machine?
    I did put the MBP to sleep during the night and today it was no issue to wake it up almost the external display did not wake up I needed to open up the MBP's screen and then the external display did wake up.
    The only differens from when it did crash is that I have the Charger cable (USB-C) in an other port, before when it did crash I did have the charger cable in the Apple HDMI/USB-C/USB-A adapter.

    I did search in Console after failure and I did find something that was named "unknown". I have 7 of them and it did start yesterday at 19:55 it's after I did buy the adapter, screen etc.
    Code:
    com.apple.message.domain: com.apple.assumes.failure
    com.apple.message.signature: xxxx
    com.apple.message.signature2: 0x5
    com.apple.message.signature3: com.apple.telemetry
    com.apple.message.summarize: YES
    SenderMachUUID: xxxx
    

    The log file for the "Sleep Wake failure" is so long so I can't write it out here in plain text so I did attach a PDF file and also the file from Console, it's the same but someone maybe like to read it in PDF instead of in console. And I could not upload the Console file in .diag extension so I needed to zip it first and then upload it.

    I did attache the files in this post and I did also upload it on a external site, just to make sure you can download the / view them.

    Download the .diag file here:
    http://www.megafileupload.com/1q7c5/Sleep_Wake_Failure_2017-02-12-191335_Robins-MacBook-Pro.diag.zip

    Download the .PDF file here:
    http://www.megafileupload.com/1q7c6/sleep_wake_failure.pdf
     

    Attached Files:

  2. Calby, Feb 13, 2017
    Last edited: Feb 13, 2017

    Calby thread starter macrumors 6502

    Calby

    Joined:
    Dec 30, 2015
    Location:
    Sweden, Gävle
    #2
    Hmm according to AASP the backorder for the logic board is 2 months here in Sweden and he told me that it's 50/50 that its a hardware issue.
    Maybe the GPU or USB-C controller card according to him.

    Edit:
    Did talk to an other AASP and he did think that this is 90% HW issue.

    This is hard, as I still can use it I don't want to be in line for a repair that 'll take around 2 months.
    I did call AppleCare and they are investigating the issue, well I don't know what that mean as they did not show any interest in the issue and that I did need to beg them to take it further.

    Hoping that AppleCare can replace the MBP as I do need it for school and I can't wait for 2 months for it to get repaired!
     
  3. Calby thread starter macrumors 6502

    Calby

    Joined:
    Dec 30, 2015
    Location:
    Sweden, Gävle
    #3
    I did find something intressting.

    2017-02-12 19:13:27.423139+0100 localhost kernel[0]: (AppleACPIPlatform) ACPI: sleep states S0 S3 S4 S5

    2017-02-12 19:13:27.452447+0100 localhost kernel[0]: PMRD: Sleep failure code 0x00000002 0x04000014

    2017-02-12 19:13:27.452449+0100 localhost kernel[0]: Sleep failure code 0x00000002 0x04000014

    2017-02-12 19:13:27.999825+0100 localhost kernel[0]: PMRD: System was rebooted due to Sleep/Wake failure

    2017-02-12 19:13:27.999826+0100 localhost kernel[0]: System was rebooted due to Sleep/Wake failure



    And before that it was many request from Bluetooth but it was 5min before the failure.
     

Share This Page