rMBP 13" 2015 Wakes itself up?

Discussion in 'MacBook Pro' started by drz, Aug 25, 2015.

  1. drz macrumors newbie

    Joined:
    Aug 25, 2015
    #1
    Yesterday as I was leaving school I put my rMBP to sleep, and I dropped it off at home in my bag and went out for the night. Today when I tried to wake it for my first class, it wasn't waking up. I had to press the power button, and once it turned on the battery had drained almost 40% (went from 60% to about 21%), and all my previously open programs were closed.

    I checked the logs, and about 4 hours after originally putting in on sleep there's this (i've never even used an SD card btw):
    8/24/15 7:57:44.000 PM kernel[0]: The USB device Card Reader (Port 3 of Hub at 0x15000000) may have caused a wake by being disconnected

    and all of these:

    8/24/15 7:57:45.000 PM kernel[0]: ARPT: 41989.669612: VendorID check failed! vendorId[ffff] != 14e4, issuing PCIe secondary bus reset
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.851971: Vendor ID 0xffff is not valid
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.852029: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.852109: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.852127: Vendor ID 0xffff is not valid
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.967307: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.981897: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.981913: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.983407: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.990441: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41991.991866: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.024893: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.036694: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.037426: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.037443: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.037462: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.039223: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.039241: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.054817: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.054850: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:47.000 PM kernel[0]: ARPT: 41992.054867: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]
    8/24/15 7:57:48.000 PM kernel[0]: ARPT: 41992.852310: wl_nocard_war: No card detected! Trying to recover, setPOWER(OFF)
    8/24/15 7:57:48.000 PM kernel[0]: ARPT: 41992.964435: wl_nocard_war: No card detected! Trying to recover, setPOWER(ON)
    8/24/15 7:58:00.000 PM kernel[0]: ARPT: 42004.681531: wl0: setup_keepalive: interval 594, retry_interval 30, retry_count 10

    these lines were the last before I turned it on this morning:

    8/24/15 7:58:01.000 PM kernel[0]: [0x42c846000, 0x40000000]
    8/24/15 7:58:01.000 PM kernel[0]: [0x0, 0x0]
    8/24/15 7:58:01.000 PM kernel[0]: kern_open_file_for_direct_io(0) took 7 ms
    8/24/15 7:58:01.000 PM kernel[0]: Opened file /var/vm/sleepimage, size 1073741824, partition base 0x0, maxio 2000000 ssd 1
    8/24/15 7:58:01.000 PM kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5



    My theory for what happened is the laptop somehow woke up when trying to deep sleep and overheated (?) while in my cramped bag. Is that possible? I haven't made any changes to the machine other than installing Pushbullet in Safari (which i've disabled for now to see if it happens again).

    Any clue what happened? I'm on the latest version of Yosemite and I haven't done any real "tweaks" to my OS.
     
  2. Taz Mangus macrumors 68040

    Taz Mangus

    Joined:
    Mar 10, 2011
    #2
    I would suggest that you give AppleCare a call and explain the situation. You might need to bring the computer into an AppleStore to have it looked at.
     

Share This Page