MBA 13": wakes up on its own from sleep (within 10 seconds)

Discussion in 'MacBook Air' started by gerbe, Sep 10, 2011.

  1. gerbe macrumors newbie

    Joined:
    Sep 6, 2011
    #1
    Hello everyone, my new MBA 13" (mid 2011) recently began to wake itself up from sleep, usually within 10-15 seconds of me setting it to sleep. The system log gives the following:

    Code:
    Sep 10 19:46:48 Air kernel[0] <Debug>: Wake reason: EHC2
    Sep 10 19:46:48 Air kernel[0] <Debug>: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
    Sep 10 19:46:48 Air kernel[0] <Debug>: The USB device Apple Internal Keyboard / Trackpad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    
    I don't have anything plugged into the USB ports and can't think of anything that I've done recently to cause this. The only recent changes I'd made were:

    • Used thunderbolt port (to connect to an external display)
    • Installed Flash and ClickToFlash
    • Installed printer drivers (Brother laser printer)

    I've tried resetting the PRAM and SMC and have tried creating a new user account, but the problem still persists. I've also turned off the wireless network (and turned off "wake from wi-fi"). This happens when I set the computer to sleep from the menu bar or when I let the computer idle to sleep (at least when connected the wall plug).

    Has anyone had similar experiences or suggestions?
    Thanks,
    G
     
  2. fschweig macrumors newbie

    Joined:
    Sep 16, 2011
    #2
    hi,

    i'm facing exactly the same issue.

    13" MBA mid 2011, i7, 265GB, 10.7.1, EFI update

    everytime the MBA falls asleep, some seconds later it wakes up again, syslog showing up the same lines as you mentioned.

    no running apps, no usb device connected, bluetooth and wifi deactivated.

    apple care advised me to delete the following files followed by a restart:

    Library/Preferences/Systemconfiguration/com.apple.Powermanagement.plist
    and Library/Preferences/Systemconfiguration/com.apple.AutoWake.plist

    unfortunately it didn't work for me...
     
  3. gerbe thread starter macrumors newbie

    Joined:
    Sep 6, 2011
    #3
    Hi fschweig, sorry to hear that you're having the same problems. I tried looking through the console and I get the following messages over the time when I try to put the computer to sleep:

    Code:
    Sep 15 21:17:55 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002ed
    Sep 15 21:17:55 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0x00000000
    Sep 15 21:17:55 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002ed
    Sep 15 21:17:55: --- last message repeated 1 time ---
    Sep 15 21:17:55 mymacbook-Air kernel[0]: 
    Sep 15 21:17:55 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0x00000000
    Sep 15 21:17:55 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002ed
    Sep 15 21:17:59: --- last message repeated 2 times ---
    Sep 15 21:17:59 mymacbook-Air kernel[0]: Wake reason: EHC2
    Sep 15 21:17:59 mymacbook-Air kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
    Sep 15 21:17:59 mymacbook-Air kernel[0]: Previous Sleep Cause: 5
    Sep 15 21:17:59 mymacbook-Air kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    Sep 15 21:17:59 mymacbook-Air kernel[0]: HID tickle 137 ms
    Sep 15 21:17:59 mymacbook-Air kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    Sep 15 21:17:59 mymacbook-Air kernel[0]: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3047 goto Exit
    Sep 15 21:18:00 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002ed
    Sep 15 21:18:00 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0x00000000
    Sep 15 21:18:00 mymacbook-Air kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002ed
    
    That's with my wireless turned off. If my wireless is on there are a few additional lines that seem to refer to it. The computer wakes itself up either way.

    One thing I've noticed is that if I let my computer fall asleep from idleness, it stays asleep properly and does not generate any console messages.

    I'm still going back and forth with AppleCare about this; they seem confident that they'll be able to figure out what's going on.

    Cheers,
    Gerbe
     
  4. gerbe thread starter macrumors newbie

    Joined:
    Sep 6, 2011
    #4
    One more thing I've noticed: I go to System Preferences -> Desktop & Screen Saver -> Hot Corners and set a hot corner for "put display to sleep," then my computer seems to go to sleep just fine without waking itself up or causing any kernel messages in the console.

    (Is there a difference between putting the computer to sleep and just putting the display to sleep?)

    Best,
    Gerbe
     
  5. fschweig macrumors newbie

    Joined:
    Sep 16, 2011
    #5
    hi,

    monitor & display sleep aren't the same, I guess.

    what do you mean with "fall asleep from idleness"?
    e.g. when I set the duration for computer standby to 5 minutes (in the energy saving prefs), it falls asleep after those 5 minutes, but instantly wakes up again.

    this isn't the only issue I'm facing with my MBA, but meanwhile the most annoying one.
     
  6. gerbe thread starter macrumors newbie

    Joined:
    Sep 6, 2011
    #6
    Hi fschweig, by idleness I think I mean the same thing that you do: from the Energy Saver preference pane in System Preferences, there are options to set the time for 'computer sleep' and 'display sleep.' If my MBA falls asleep due to these options (rather than going from the apple menu and clicking "sleep") then I don't seem to get any self-waking behavior or weird console messages.

    -Gerbe
     
  7. fschweig macrumors newbie

    Joined:
    Sep 16, 2011
    #7
    how glad you are... because when i want to use my external display, there isn't a single way to enter the sleep mode.

    sleeping by closing the lid isn't possible because of lions new handling with displays
    sleeping by choosing sleep from the apple menu doesn't work
    sleeping by pushing the power button doesn't work
    sleeping after some minutes idleness doesn't work...

    so every time i want my MBA to sleep, i have to unplug the mini display port and close the lid.

    how stupid is that?
     
  8. gerbe thread starter macrumors newbie

    Joined:
    Sep 6, 2011
    #8
    Hmm... my problems started after I first tried out my thunderbolt/display port to use an external display. (Though it persisted after I unplugged it.) I wonder if it's related to this. If you look at the console messages I posted, they begin with a message from the Thunderbolt drive. Maybe it has something to do with this.
     
  9. fschweig macrumors newbie

    Joined:
    Sep 16, 2011
    #9
    below you can see my console entries.

    Code:
    18.09.11 11:46:15,000 kernel: en0: BSSID changed to 00:80:48:57:ac:e5
    18.09.11 11:46:15,000 kernel: wlEvent: en0 en0 Link DOWN
    18.09.11 11:46:15,000 kernel: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
    18.09.11 11:46:20,000 kernel: Wake reason: EHC2
    18.09.11 11:46:20,000 kernel: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
    18.09.11 11:46:20,000 kernel: Previous Sleep Cause: 5
    18.09.11 11:46:20,000 kernel: en0: 802.11d country code set to 'X3'.
    18.09.11 11:46:20,000 kernel: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
    18.09.11 11:46:20,000 kernel: The USB device Apple Internal Keyboard / Trackpad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    
    is there anybody reading this thread, who's able to help?
     

Share This Page