|
|
MacBook wakes from sleep by itself
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
Every time I send this MacBook to sleep it wakes straight back up again. If I close the lid it sleeps but then the Apple logo on the lid flashes as it tries to wake up. If left it drains the battery and heats up lovely. If I sleep it via the menu command and leave the lid up, it just pops back to life again after about 20 seconds.
At first I thought it was a bluetooth issue but even with BT turned off it behaves like this. I swapped the drive with another Mac and the other Mac sleeps fine while this one still wakes, so it's not a system setting.
I've grabbed the console log around sleeping but I can't see anything obvious related to wake from sleep. I guess it's a logic board issue but was rather hoping it would be a module attached to the logic board (I'm looking at you bluetooth module which I could swap out.
Here's the log around the sleep command in case anyone can see anything I'm missing:
Jul 25 22:19:00 andrews-imac loginwindow[40]: loginwindow SleepWakeCallback WILL sleep
Jul 25 22:19:00 andrews-imac kernel[0]: AFPSleepWakeHandler: going to sleep
Jul 25 22:19:02 andrews-imac configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slow response 1992 ms
Jul 25 22:19:03 andrews-imac com.apple.launchd.peruser.503[170] (com.akamai.client.plist[392]): Bug: launchd_core_logic.c:4139 (24108):13
Jul 25 22:19:03 andrews-imac com.apple.launchd.peruser.503[170] (com.akamai.client.plist[392]): posix_spawn("/Applications/Akamai/loader.pl", ...): No such file or directory
Jul 25 22:19:03 andrews-imac com.apple.launchd.peruser.503[170] (com.akamai.client.plist[392]): Exited with exit code: 1
Jul 25 22:19:03 andrews-imac com.apple.launchd.peruser.503[170] (com.akamai.client.plist): Throttling respawn: Will start in 10 seconds
Jul 25 22:19:04 AndrewsMacBook configd[15]: setting hostname to "AndrewsMacBook.local"
Jul 25 22:19:04 AndrewsMacBook configd[15]: network configuration changed.
Jul 25 22:19:17 AndrewsMacBook loginwindow[40]: loginwindow SleepWakeCallback will power on, Currenttime:7/25/2010 10:19:17.001 PM - Waketime:7/25/2010 10:19:17.000 PM = Deltatime:0.001138091
Jul 25 22:19:17 AndrewsMacBook configd[15]: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slow response 113 ms
Jul 25 22:19:17 AndrewsMacBook configd[15]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slow response 114 ms
Jul 25 22:19:17 AndrewsMacBook configd[15]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slow response 115 ms
Jul 25 22:19:17 AndrewsMacBook mdworker[168]: Error loading bundle (PHXLocalSource): Error Domain=NSCocoaErrorDomain Code=4 UserInfo=0x102e7b390 "The bundle “LocalSourceBundle” couldn’t be loaded because its executable couldn’t be located."
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Tried an SMC or PRAM reset?
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
Originally Posted by seanc
Tried an SMC or PRAM reset?
Oh yes. Both. Several times.
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Disabling Airport before sleep?
Airport is still on it's own card isn't it?
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
Originally Posted by seanc
Disabling Airport before sleep?
Airport is still on it's own card isn't it?
Yup. Airport and BT switched off. Still does it.
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Well that's me out of ideas for hardware, other than the logic board or possibly a damaged reed switch cable - if they still have those. Maybe its had a liquid spill?
Can you try a fresh install of 10.6 or some form of 10.5 (if supported) to rule out a bug in some kext?
Can you test an Ubuntu live disc?
Can you, power on the Macbook, unplug the top case and sleep it via USB keyboard and mouse?
|
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2001
Location: Wasilla, Alaska
Status:
Offline
|
|
Which exact model are we talking about here?
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
It's the first version of the Uni MacBook late 2008 model
Done a clean install of both 10.5 and 10.6
Can't test it with Ubuntu easily, ie without creating disk
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Posting Junkie
Join Date: Mar 2004
Location: UK
Status:
Offline
|
|
Your log should have a "reason for wake" listed somewhere followed by a code. Did you choose 'all messages' before copying the log?
|
I have plenty of more important things to do, if only I could bring myself to do them....
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2001
Location: Wasilla, Alaska
Status:
Offline
|
|
You should check the connector on the logic board for the sleep sensor. It's located in the bottom right hand corner of the logic board. It's a tiny little thing. You can see it just above and to the left of the black area on the trackpad in this iFixit picture:
The sleep sensor itself is part of the hard drive bracket.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
Thanks AK
Managed to track this message down from the Console
26/07/2010 23:45:30 kernel hibernate_write_image done(0)
26/07/2010 23:45:30 kernel sleep
26/07/2010 23:45:30 kernel Wake reason = OHC1
26/07/2010 23:45:30 kernel System Wake
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:261 powerStateWillChangeTo: flags=82 stateNumber=4
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:262 powerStateWillChangeTo: found flag=kIOPMPowerOn (2)
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:267 powerStateWillChangeTo: found flag=kIOPMRestartCapability (80)
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:261 powerStateDidChangeTo: flags=82 stateNumber=4
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:262 powerStateDidChangeTo: found flag=kIOPMPowerOn (2)
26/07/2010 23:45:30 kernel /drv/ MacModule.cpp:267 powerStateDidChangeTo: found flag=kIOPMRestartCapability (80)
26/07/2010 23:45:30 kernel Previous Sleep Cause: 5
26/07/2010 23:45:30 kernel The USB device Apple Internal Keyboard / Trackpad (Port 6 of Hub at 0x4000000) may have caused a wake by issuing a remote wakeup
Seems the trackpad may be issuing spurious input causing it to wake. When I close the lid it doesn't seem to generate the same error though. Although it still repeatedly wakes up before sleeping again.
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
OK so it's the same error when I shut the lid so the issue is either the keyboard/trackpad itself OR the USB bus that the trackpad is on.
I suppose I could disconnect the trackpad and kbd to see what happens then. Strangely I have noticed that if I connect a USB or BT keyboard, after a while the modifier keys on the external keyboard start to misbehave, so the shift key stops working to constrain selections etc or to enable multiple selections. A restart cures this but it looks like part of the same issue.
NOt happy if it's the USB controller on the mobo though.
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Posting Junkie
Join Date: Mar 2004
Location: UK
Status:
Offline
|
|
|
I have plenty of more important things to do, if only I could bring myself to do them....
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Oct 2008
Location: UKland
Status:
Offline
|
|
So I disconnected the trackpad and keyboard connectors to the logic board and connected an external keyboard and the MacBook slept like a baby. Reconnecting the keyboard was good also but as soon as I connected the trackpad back in the problem recurred. Bad trackpad then.
Best I get a new one. Hopefully the fault IS in the actual trackpad, generating spurious signals rather than in the actual trackpad usb bus.
|
This space for Hire! Reasonable rates. Reach an audience of literally dozens!
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Could be the cable for the trackpad, glad you've isolated the problem.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|