Just picked up a new MacBook Pro last night. Seems like a very nice machine (coming from a rev B, 1st gen MBP). An oddity, though. When closing the lid to put it in sleep mode it seems to awaken for a few seconds every 45 seconds. There will be an audible bzz-bzzzt (as if the hard drive spun briefly), then the apple logo light built into the lid illuminates for a few seconds. It then extinguishes and 45 seconds later the pattern repeats.
I'm not seeing anything in Energy Saver settings to tweak for this. Any ideas?
MacBook Pro 2.53ghz 15" (late 2008) MacBook Pro 2.33ghz 15" PowerBook G4 1.33ghz 12",
Mac OS X (10.4.10)
I think i did the same thing before mine freaked out on me. I probably shut the laptop then unplugged the USB mouse -- after all, this is what I always did with my PowerBook G4. Then apparently my new laptop decided it was time to take a sauna.
Before I close my lid, I unplug all peripherals (ethernet, power, mouse, etc.). Then I close the lid and it goes to sleep no problem. When I get to where I'm going, I have to open the lid first before plugging anything back in. So far no sleep issues.
If I try to plug my mouse in before opening the lid, my computer won't wake up. If I unplug my mouse after I close the lid, I have sleep issues.
This is how the MacBooks are designed to function. If you have any type of peripheral plugged into them after putting it to sleep, unplugging the peripheral will wake it back up. BUT I should also note the MacBook should go right back to sleep if the lid is shut when you unplug the peripheral.
The problem we are having is the MacBooks waking up all on their own. Nothing is plugged into them when it happens. I've had it do it even after turning off Bluetooth and Airport before shutting the lid.
This thread is getting deep and my posts from all of my extensive troubleshooting are falling further and further back so let me just say this again in case any newcomers are reading this:
I am on my FOURTH MacBook Pro because of this sleep issue. I do believe this is a software issue. I say this because when I took the third one back to the Apple store, I specifically requested they swap the hard drives from it to the new one which is now my fourth. Not but one hour after I got home, the Mac woke up from sleep mode. I began to think this just isn't going to work and was about ready to take it back for a full refund and sit on the sidelines until Apple can come up with a resolution. But before doing so, I figured I would try the reformat/reinstall once more. So I did.
It's been over a week since the reformat/reinstall and I have not had the sleep issue occur at all. I have made sure to take baby steps this time around meaning I have installed software day by day as well as attaching my peripherals. Today was the final test with my USB mouse which was the last item on the checklist. Everything else has been installed/attached just like the last three MacBook Pro's and so far I have not had a single problem with the Mac waking up from sleep mode.
Believe me when I say this; I have spent A LOT of time troubleshooting this issue. In fact, I have spent so much time that Apple sent me a brand new iPod Nano 8GB 4th Gen for all my troubles. I have about 5 days left before my return period is up so I am going to make sure I put the Mac to sleep extensively to make sure this issue is gone for good.
In the end, I still don't have a definitive answer as to what is causing the sleep issue. Someone did post a pretty good theory about it having to do with the Migration Assistant but I really don't know. I can say after doing the reformat/reinstall on the MacBook Pro I am using now, I did not use Migration Assistant like the other three times. I instead manually copied all of my files from the Backup.backupdb folder from my Time Machine external hard drive. But then we have people saying they are having the sleep issue and they have not used the Migration Assistant at all.
If you actually read all of this, go take a smoke break. 😉
Yes, I think that might be the cause! I sometimes have this problem and it could well be me messing with my mouse after I've closed the laptop and put it in my bag.
FWIW...I did not use it either and my unit does not wake up.
Dave M. MacOSG Founder/Ambassador  An Apple User Group  iTunes: MacOSG Podcast Creator of 'Mac611 - Mobile Mac Support' (designed exclusively for an iPhone/iPod touch)
I am getting the same issue. I had a Macbook Pro that I exchanged for this one for an unrelated reason. I used the migration assistant to copy my files from the old macbook pro to this one. The old macbook pro did not suffer from this issue at all.
Just to clarify, I am suffering from the close the lid to find the machine burning hot half an hour later.
I am taking this back to the apple store as soon as I can for a replacement 🙂
I've had my 2.4GHz model for 10 days now and haven't had any problems getting the macbook pro to go into sleep mode. I take it to all my classes and when I'm ready to go I just close the lid and it sleeps fine. I also let it sleep overnight, and when I wake up the entire unit is really cold to the touch and it doesn't wake or come on at all while in sleep mode. Maybe it's effecting the majority of the new macbook pros and just not all.
My machine has similar issues. When I close the machine it goes to sleep normally. If I leave the machine alone it stays asleep. If I move the machine it almost immediately wakes up. The reason given in my system.log is EC.
This problem is extremely irritating but it appears to be fixable in software. Since I reset the machine by holding the power button for 10 secs the machine becomes much less sensitive to being moved when asleep.
So many improvised solutions... I just hope that apple at the very least post a reply to this thread, or prepare a quick software fix for this KNOWN issue on their newborn Macbook and Macbook Pro babies?
This solution worked for me as well - My Sandisk ExpressCard 34 flash reader was preventing proper sleep and shutdown, but SmartSleep appears thus far to solve the problem.
I've had one of the new Mackbook Pro systems for a couple of weeks now and in general have been very pleased with it. However, last Friday I hit the problem being discussed in this thread. When I raised the lid, the display stayed black. I noted that I didn't hear the usual noise the superdrive makes when it comes out of sleep. Also, the front light went from a pulsing state to a solid-on state. Since it wouldn't respond to any input and the screen stayed black, I had to power it off and restart.
After the restart, I examined the consoles looking for any differences between a successful resume from sleep and that last failed case. The only obvious difference I could see was that on the successful cases, I would see a "System Wake" message from the kernel (reason EC), and then about three seconds (and a bunch of other messages) later I would see a kernel message of "AFPSleepWakeHandler: waking up". However, on the failure case, while I see the initial "System Wake" message, the AFPSleepWakeHandler message never appears. Interestingly, the system itself appears to be quite active, processing network traffic and such. It just isn't driving the display, and it's not clear to me whether it is responding to any peripheral input.
I assumed this was probably a firmware issue with either the new Macbook Pros or the new Macbooks in general.... Until Sunday night. On Sunday I was working with my old 2+ year-old Macbook (one of the original Core Duo models). When I went to bring it out of sleep Sunday night...Bam...Black screen with the exact same symptoms. I have had this machine for over two years and it has been through hundreds of sleep/resume cycles, and the first time this happens is two days after it happens on my new Macbook Pro? Hmmm.... It makes me really suspect this is more of a bug in 10.5.5, or some other recent Apple software maintenance.
After reading this thread, I am testing the SmartSleep workaround on both systems, hoping that will help. (And even if it doesn't, I'm already preferring the much faster time-to-sleep behavior on my Pro. I don't really benefit from the hibernation anyway.)
YES! This seems to have worked! Disabling the function for bluetooth to wake this computer. This must be caused by all the bluetooth signals in the air 🙂
