I've been having this problem for almost a year. Whether I just close the MBP or actually go to "Apple" then "sleep" my MBP will come awake. If it is closed, the Apple will light up and the disk drive will make a noise like it is ejecting. If it is open and I put it to sleep, it just simply wakes up.
I've tried almost everything to resolve this issue:
- Bluetooth is turned off
- I tried the command line prompt that makes it only wake up if a key is pressed (this worked for a while, but only if I left the lid open, which I didnt mind. About a week ago it stopped working all together)
- Reset the PRAM
- And today I went to Apple and bought Snow Leopard (since I was only using Leopard), formatted my HD and upgraded my OS
and its still doing it!! I know I should just bring it in to an Apple store, but I thought the last one would fix the problem...
So if anyone has any other solutions please let me know!
That is why I think that it must be something that I run which alters the OS. This implies a hole in the system that should be plugged.
After my erase and re-build my only login item is iTunesHelper. The only things I had in common with you were, I think,
gfxCardStatus
GrowlHelperApp
I also had and still have SmartSleep, still set for Sleep only. Even so, the auto-wake problem has been solved for me.
I agree that onset occurs only after some time has passed since booting. Re-booting always fixes it, but the problem recurs after periods of time that have ranged from a few minutes to a few days. The problem occurs on all accounts.
My problem should have been recorded by Willow Bend Apple Store in Plano, TX. A genius there looked at this forum. My experiences are pretty well documented here and on the other one referenced above.
The only thing I've done is to access the USPS site for postage and labels for packages (it's that time of year.) I had to download and install Acrobat Reader. (I had zapped Reader long ago and use only Preview-- but the USPS site has some file format that Preview doesn't recognize. Darn.)
At about the same time, Time Machine stopped updating. I didn't notice any of this until this morning when I saw that the laptop was not asleep. That's when I found that Time Machine was not recognizing the sparsebundle of my backup. It was quite awkward to reconnect. Is this a coincidence?
The kernel logs for times before midnight this morning have disappeared; apparently waking and sleeping all night was so much activity that the logs filled up.
I booted, sleep returned, but the auto-wake problem reappeared soon after a Time Machine backup. I've re-booted and been up for 2 1/2 hours, now, with backups, etc. Reader is still on my system. I've got console open and I'm forcing sleep every 30 min or so just to see.
I'm beginning to suspect an alien conspiracy. Perhaps the coming lunar eclipse will fix everything.
The solstice lunar eclipse did not fix it. I'm giving up on astrology.
I installed label printer software so I could do Christmas cards, and it required a re-boot. I'd been auto-wake free for two days. It continued to do OK, but later last evening it suddenly re-started. I had a normal wake by opening the lid, messed around on the web, then closed the lid, and, wham, it was awake. The only thing that happened between normal sleep/wake and the auto-wake was a time machine backup. Could this be connected? This is the log from normal wake to ECH1 wake-- I see nothing except the TM backup, but I don't know how to read these things:
Dec 21 20:50:40 MBP kernel[0]: Wake reason = EC LID0
Dec 21 20:50:40 MBP kernel[0]: System Wake
Dec 21 20:50:40 MBP kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 4)
Dec 21 20:50:40 MBP kernel[0]: Previous Sleep Cause: 5
Dec 21 20:50:40 MBP kernel[0]: en1: 802.11d country code set to 'X0'.
Dec 21 20:50:40 MBP kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Dec 21 20:50:42 MBP kernel[0]: vmnet: VMNetDisconnect called for port 0x9f37f00
Dec 21 20:50:42 MBP kernel[0]: vmnet: bridge-en1: filter detached
Dec 21 20:50:42 MBP kernel[0]: vmnet: bridge-en1: down
Dec 21 20:50:42 MBP kernel[0]: vmnet: bridge-en1: detached
Dec 21 20:50:42 MBP kernel[0]: vmnet: Freeing hub at 0x13d33800.
Dec 21 20:50:42 MBP kernel[0]: AFPSleepWakeHandler: waking up
Dec 21 20:50:43 MBP kernel[0]: en1: 802.11d country code set to 'US'.
Dec 21 20:50:43 MBP kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Dec 21 20:50:47 MBP kernel[0]: Auth result for: 00:1f:5b:87:c3:e9 MAC AUTH succeeded
Dec 21 20:50:47 MBP kernel[0]: AirPort: Link Up on en1
Dec 21 20:50:47 MBP kernel[0]: AirPort: RSN handshake complete on en1
Dec 21 20:50:48 MBP kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x13ce9200.
Dec 21 20:50:48 MBP kernel[0]: vmnet: VMNetConnect: returning port 0x13ce9200
Dec 21 20:50:48 MBP kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 21 20:50:48 MBP kernel[0]: vmnet: Allocated hub 0x13d33800 for hubNum 0.
Dec 21 20:50:48 MBP kernel[0]: vmnet: VMNET
SOBINDTOHUB: port: paddr 00:50:56:f8:69:23
Dec 21 20:50:48 MBP kernel[0]: vmnet: Hub 0
Dec 21 20:50:48 MBP kernel[0]: vmnet: Port 0
Dec 21 20:50:48 MBP kernel[0]: vmnet: bridge-en1: got dev 0x8c80e04
Dec 21 20:50:48 MBP kernel[0]: vmnet: bridge-en1: wireless interface detected.
Dec 21 20:50:48 MBP kernel[0]: vmnet: bridge-en1: up
Dec 21 20:50:48 MBP kernel[0]: vmnet: bridge-en1: attached
Dec 21 20:50:48 MBP kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x13ce9200.
Dec 21 20:50:50 MBP kernel[0]: utun
ctlconnect: creating interface utun0
Dec 21 20:51:26 MBP kernel[0]: AFP_VFS afpfs_mount: /Volumes/My Book, pid 1473
Dec 21 20:53:29 MBP kernel[0]: AFP_VFS afpfs_unmount: /Volumes/My Book, flags 0, pid 1499
Dec 21 20:53:29 MBP kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 19 error 89 reqID 16273 flags 0x9 afpCmd 0xF0000002 so 0xa29c330
Dec 21 21:03:09 MBP kernel[0]: AFPSleepWakeHandler: going to sleep
Dec 21 21:03:09 MBP kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 21 21:03:09 MBP kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 21 21:03:10 MBP kernel[0]: vmmon: powerStateDidChange flags=0x4 (state 2)
Dec 21 21:03:10 MBP kernel[0]: System Sleep
Dec 21 21:03:11 MBP kernel[0]: Wake reason = EHC1
The console message states that it work because of EHC1. EHC is the Enhanced Host Controller for USB. So, a USB device, or something that the system believes to be a USB device (for example, Bluetooth on the Mac goes through USB), has woken it up.
Check your peripherals. Make sure that you have 'Allow Bluetooth devices to wake this computer' unchecked in the Bluetooth advanced settings (otherwise your mobile phone might wake your computer).
Yeah, this post has been going on for quite a while. You may have seen from earlier posts that those few of us getting this auto-wake experience have bluetooth off and no USB devices connected. EHC2, by the way, seems to be the keyboard. No one, including the geniuses, has a really good answer about how EHC1 occurs with nothing connected. That, really, is the puzzle. If you read this entire thread and have some ideas, please help us out!
I'm pretty convinced it's not the lid switch, at least in my case. If it were, then the kernal log would indicate a lid opening, "Wake reason = EC LID0" instead of "Wake reason = EHC1." If you haven't looked at the kernal log, you should run Console (applications/utilities/console.app) and point to files/private/var/log to find the file kernal.log and search for "wake reason" If you see something interesting, let us know.
This is certainly maddening. I'll keep you informed!
Well, as suggested earlier in the thread, I opened a case and took my machine to the mobbed Apple store last night. Genius wants to replace the reed switch, though I don't think this will fix anything. I didn't leave it for the overnight repair because I need my machine for now and the crowd at the store was insane. I'll maybe wait until next week for things to calm down a bit.
In any case, a friend gave me a tip to check whether it's the iSight camera causing the problem. If you are able to get back into the failure mode again (I haven't myself for the past 2 or 3 days), try opening Photobooth and see if you lose the camera at any point. I'm told that EHC1 on our machines refers to the USB hub for 3 devices: the camera, the IR receiver, and USB port "B", presumably the port closer to the display. You can see these listed together in System Profiler. Also try refreshes in ASP to see if any of the devices disappear and/or reappear on the USB bus.
Has anybody got any further with this? Its driving me barmy now. Sometimes my macbook happily goes to sleep. Other times it does not, guaranteed it's always the time I just set it to sleep and walk off without realising its woken straight up again. Once it decides it's not going to sleep, the only way to cure it is to reset it, then it will sleep again fine!
I too have checked log and wake reason is EHC1.
Most of the time my macbook is in clamshell mode these days connect to a 27" apple screen which I recently purchased (although the problem was there before I bought the screen).
So Lid is always closed. One thing I have noticed which I'm not sure if anybody else has noticed (or perhaps I'm just clutching at straws) is that I'm sure when it decides it's not going to sleep it appears to do the going to sleep bit, much much quicker. As in you click sleep in the menu or press the correct combination of buttons and the screen immediately shuts off and the power light goes out, then it all fires straight back up.
When it's working ok it takes a little longer to actually go into sleep mode. Has anybody else noticed this? It's as if it goes to sleep so fast it wakes it's self back up to finish shutting down!
It's obviously a genuine problem because so many of us are suffering from it. On my last upgrade I hoped it would go away but it hasn't because I'm stuck in zombie mode now, it just won't sleep.
Something needs to be done! Mac need to investigate this somehow instead of their usual denying it's a problem and it must be our fault!
oh and I've tried the usual of shutting down all open bits of software, but I run the same lot of software all the time (I'm a web developer and host) so there is no simple explanation that it's just running a certain bit of software.
I've had the same issue as you for a long time now. I think I tried everything you have. Put now I'm trying smc-reset again. Gonna have look att the tip about iSight
/pascal
Still no luck! It's totally gone over my head now, I can't find any reason as to why it happens, I'm sure it's happening more often now. My macbook ends up being on 24/7 without me realising, can't be doing it any good! Typical that Apple don't recognise this as a problem when so many of us suffer form it.
Celtic Web Solutions wrote:
when so many of us suffer form it.
Actually, there seem to be very few affected by this. I think that I am the first to post about this problem, starting in June, and I'm not sure there have been as many as 15 people who have responded. Some of those that did never posted again, perhaps finding that the problem was different than the one we are discussing (perhaps bluetooth initiated, or somesuch.)
I have not had a recurrence in nearly a month. What seems to have fixed it for me is some combination of re-installing the OS, migrating all but my user library, and SMC resets.
I have the same issue when I use the keyboard shortcut to put the MBP to sleep, however when I click Sleep in the Apple menu it stays in Sleep mode. Bit strange :/
