Mac Pro Keeps Being Woken Up By Bluetooth I Think???

Discussion in 'Mac Pro' started by rossagrant, Apr 20, 2011.

  1. rossagrant macrumors member

    Joined:
    Mar 3, 2009
    #1
    Hi guys,
    Pulling my hair out with this one as I'm one of those types that wants a fix and not a workaround.

    A couple of days ago I put my Mac Pro to sleep before I got into bed as I usually do.

    I was just drifting off to sleep and the thing decided to wake up on it's own. I put it back to sleep and I thought nothing of it until about 30 mins later it did it again.

    Now I reset the PRAM, reset the SMC, trashed the powermanagement.plist and this didn't have an affect.

    I then thought actually, why not do a fresh install of Snow Leopard as it's been running for sometime now and I had a lot of software installed I didn't use so I thought why not.

    It's STILL doing the same thing.

    Now the log says:

    20/04/2011 15:40:21 kernel en0 Link down
    20/04/2011 15:40:21 kernel en1 Link down
    20/04/2011 15:40:22 kernel System Sleep
    20/04/2011 15:40:22 kernel Wake reason = UHC6
    20/04/2011 15:40:22 configd[13] network configuration changed.
    20/04/2011 18:11:34 Spotify[568] Reachability Flag Status: -R tc----- networkStatusForFlags
    20/04/2011 18:11:34 Spotify[568] Reachability Flag Status: -R tc----- networkStatusForFlags
    20/04/2011 18:11:34 kernel System Wake
    20/04/2011 18:11:34 kernel Previous Sleep Cause: 5
    20/04/2011 18:11:34 kernel The USB device BRCM2046 Hub (Port 1 of Hub at 0x5a000000) may have caused a wake by issuing a remote wakeup (2)
    20/04/2011 18:11:34 kernel The USB device Bluetooth USB Host Controller (Port 1 of Hub at 0x5a100000) may have caused a wake by issuing a remote wakeup
    (3)
    20/04/2011 18:11:34 kernel EIR is supported.
    20/04/2011 18:11:34 kernel SSP is supported.
    20/04/2011 18:11:37 kernel Ethernet [Intel82574L]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af48,0de1,0200,cde1,3c00]
    20/04/2011 18:11:39 ntpd[42] bind() fd 25, family 30, port 123, scope 5, addr fe80::ea06:88ff:fecc:3b61, in6_is_addr_multicast=0 flags=0x11 fails: Can't assign requested address
    20/04/2011 18:11:39 ntpd[42] unable to create socket on en1 (13) for fe80::ea06:88ff:fecc:3b61#123
    20/04/2011 18:11:40 kernel en0 Link down

    So I am presuming it's a bluetooth device, which is either my magic mouse or my apple wireless keyboard causing the issue.

    Could it be a dodgy bluetooth card though?

    It hasn't had this problem ever before so I was also thinking it's maybe due to the recent 10.6.7 update which I read caused some trouble with bluetooth devices on some other macs.

    It's just really bizarre.

    I can turn off the 'allow bluetooth devices to wake this computer' and see if that helps but I have NEVER had to change this default setting before which would suggest some other conflict, a faulty mouse or keyboard or a faulty bluetooth card.

    I don't want to just fix the symptom if the underlying problem is faulty hardware as I would rather have the offending article swapped out whilst I still have applecare.

    Has anyone else experienced this lately???

    Really appreciate you reading this so thanks!

    Ross :)
     
  2. rossagrant thread starter macrumors member

    Joined:
    Mar 3, 2009
    #2
    Hi all,
    Just incase anyone stumbles across this thread when they are having similar issues I wanted to post an update.

    It sounds so simple but I think my wake issues may have actually just been down to weak batteries in my keyboard.

    After 10.6.7 some people were reporting that they were getting the wrong battery life metering for wireless devices. Some people had their power levels stuck at 100% even though the batteries had previously been showing 50% depletion before updating to 10.6.7

    My keyboard was showing 46% yesterday but I thought to eliminate the possibility of the mac pro waking due to a lost keyboard connection due to weak batteries, I changed them out for fresh batteries.

    My mac went to sleep last night and slept the whole night, until I woke it this morning.

    I'll try it again later but I'm pretty certain that's all it was.

    Oh well, at least I've got a freshly installed OS and clean running machine now, even though all I actually needed to do was swap some batteries! :)
     
  3. stiwi macrumors regular

    Joined:
    Nov 13, 2010
    Location:
    Singapore
    #3
    I am having the same problem since few days. I don't think it is keyboard though, despite 100% level showing up all the time. Though Mighty Monitor shows 70% and the batteries were replaced no later than 2 weeks ago, so it is definitely not a keyboard related issue due to low battery.

    Yesterday I simply took out my iphone from the dock before putting MP asleep and it didn't wake up.
     

Share This Page