You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Bluetooth drivers prevent system from sleeping in Mavericks - what's going on!?

Just installed Mavericks. My iMac 27" no longer engages the screensaver or puts the monitor to sleep as specified in preferences as a result. When I enter pmset -g assertions in Terminal, I get the following:



10/22/13, 11:03:40 PM PD

Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 1

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 16(powerd): [0x0000000900000131] 00:19:12 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"

pid 49(hidd): [0x0000000a00000194] 00:15:51 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 1170 secs Action=TimeoutActionRelease

Kernel Assertions: 0x10c=USB,BT-HID,MAGICWAKE

id=500 level=255 0x4=USB mod=10/22/13, 10:53 PM description=EHC2 owner=AppleUSBEHCI

id=503 level=255 0x8=BT-HID mod=12/31/69, 4:00 PM description=com.apple.driver.IOBluetoothHIDDriver owner=BNBTrackpadDevice

id=504 level=255 0x8=BT-HID mod=12/31/69, 4:00 PM description=com.apple.driver.IOBluetoothHIDDriver owner=AppleBluetoothHIDKeyboard

id=505 level=255 0x100=MAGICWAKE mod=12/31/69, 4:00 PM description=en1 owner=en1



I'm not terribly concerned with "ExternalMedia" as that always appeared in Mountain Lion as well but never actually prevented my system from putting the monitor to sleep. My concern is with the "UserIsActive" item as it appears to refer to "MAGICWAKE" (a google search only shows an app that I do not have installed and sheds no light on what it means in this context) and points directly to my keyboard and trackpad. Oddly, turning "Allow Bluetooth devices to wake this computer" in the Bluetooth advanced preferences does not change this, nor does rebooting. The countdown that appears here is always in the 1160 to 1195 range. I'm completly stumped...

iMac (27-inch Mid 2011), OS X Mavericks (10.9)

Posted on Oct 22, 2013 11:10 PM

Reply
Question marked as Top-ranking reply

Posted on Aug 6, 2017 8:27 PM

Nothing here. I tried of everything that all people here said.


MAC SIERRA 10.12.6


Doing "pmset -g pslog" I know this


pmset -g pslog  18:27  06.08.17

Logging IORegisterForSystemPower sleep/wake messages

pmset is in logging mode now. Hit ctrl-c to exit.

2017-08-06 18:31:14 -0300

IOPSNotificationCreateRunLoopSource

Now drawing from 'AC Power'



2017-08-06 18:31:27 -0300

IORegisterForSystemPower: ...Sleeping...



2017-08-06 19:41:01 -0300

IORegisterForSystemPower: ...HasPoweredOn...

Wake Reason = UHC1 USB3 USB5 UHC7 . //I did this on purpose to test



2017-08-06 22:58:29 -0300

IORegisterForSystemPower: ...Sleeping...



2017-08-06 22:59:07 -0300

IORegisterForSystemPower: ...HasPoweredOn...

Wake Reason = pci1106,3483


Here is the result. I first do the tests according to the tips from you guys. I restart the MAC and then I'll send it to sleep. And he sleeps beautiful. But then I hit the mouse (test only with keyboard, no keyboard, only power button and nothing) to connect again. I use the Mac for a few minutes - I analyze if it has something in "prevented by" and I send a "sudo pmset sleepnow" - It takes a while to turn off completely, then it turns on very quickly.


It is in the second "revive" that mine loses the quality of sleep.

Something on PCI is calling back my mac from sleep instantaneously.



Nothing is attached, no USB, no Bluetooth, no internet sharing, no Chrome o other "sleep prevented by". Nothing. Could Apple be nice and solve this? Creating a simple option to override according to the user's need? They made the "Caffeine" to satisfy users that they did not want to "sleep" right? Why not this demand for sleep?



This problem is getting on my nerves, consuming my patience. Every single reboot I need to rearrange my work desktops because not even that, the Sierra knows how to do it alone sometimes.


Best Regards

150 replies

Nov 19, 2013 7:14 AM in response to terriblewithcomputers

Does it seem unreasonable for me to ask the guy at Apple to have their engineering team find a machine there with the sleep assertion giving us trouble, and to work on that, rather than mess with partitions on my hard-drive...clean installs, more redundant troubleshooting and sending files...etc?


In a previous email to me, he said that this problem affects a very small number of machines, but I'm willing to bet that someone over in their engineering dept has a computer with this same problem!


Thoughts?

Nov 19, 2013 11:53 PM in response to terriblewithcomputers

Since this bug doesn't have a known serious issue as of now, only delays sleep by half a minute, I don't think it's worth clean installing and do all sorts of troubleshooting because they're too lazy.

I have a clean install and I've been seeing this bug ever since installing Mavericks.

It's that only a fraction of users notice it and care about it, causes no known harm, so apple doesn't care much either.

Nov 20, 2013 11:49 PM in response to targus

I have this exact same issue, was fast under mountain lion, slow as **** now. I will edit this page when I have time to shut it down and capture console messages.


pmset -g assertions

21/11/2013 6:35:37 pm AE

Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 0

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 87(hidd): [0x0000000a000026d9] 02:13:02 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 585 secs Action=TimeoutActionRelease

Kernel Assertions: 0x4=USB

id=501 level=255 0x4=USB mod=19/11/2013 1:28 pm description=EHC1 owner=AppleUSBEHCI

Nov 22, 2013 2:41 AM in response to targus

I've found one message common in delayed sleep events that's not present at prompt sleep:


kernel[0]: en1: BSSID changed to (MAC address)

Nov 25, 2013 5:53 PM in response to targus

Add me to the list. Late 2011 15" Macbook Pro 2.5Ghz, 16GB RAM, 750GB second-gen hybrid disk from Seagate (the stock 500 was just pitifully slow)


Granted, mine was an upgrade from Mountain Lion and not a fresh install, but given what I've seen here that seems to make no difference. Exactly the same messages on sleep and the fan runs HOT for up to two minutes before it actually goes to sleep.


Definitely a Mavericks bug... under ML it went to sleep in at most about 5 seconds.

Nov 26, 2013 8:23 PM in response to targus

Just FYI, I filed this as a bug last week. They asked me for additional system information and still haven't marked it as 'duplicated'... I will let you guys know if I get any updates.


All the other macbooks I've seen with regular drives (no ssd) and Mavericks have the same problem, so it definitely looks like a Mavericks issue.

Dec 2, 2013 2:49 PM in response to targus

Same here.


13" MBP Mid 2012.


Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 0

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 48(hidd): [0x0000000a00001421] 00:22:27 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 288 secs Action=TimeoutActionRelease

No kernel assertions.

Dec 2, 2013 2:58 PM in response to spish

Thanks for the reply.


It is apparent to me that this is NOT a problem with my machine solely, and is a bug with Mavericks...perhaps with Mavericks combined with a particular machine combo.


Let's try to all get feedback to Apple, and all of you registered developers, go out there and report this as an official BUG with Mavericks. I am hopeful that this will be fixed in a forthcoming OSX update...but we will see.


Honestly, I have almost forgot about it, because I'm used ti it, but I'd rather not have to wait half a minute for my computer to fall asleep. I have more or less just forgotten what it used to be like on Mountain Lion, which is sad.


Anyone with the same problem, complain to Apple as many times as you see fit. It is not acceptable, and the system's built in assertion status check through terminal tells us that this is not a normal occurrence.

Dec 3, 2013 3:58 AM in response to targus

So not sure how many others might fall into this... but I stumbled across this the other day "Google Chrome causes slow sleep MacBook Pro (Mountain Lion O/S)".


I started suffering from really slow sleep times after the upgrade to Mavericks on my 2011 MBP and had been watching this thread. After finding the linked Chrome bug, I tried killing Chrome and putting my MBP to sleep.... it went down in 7 sec (had been 60+)!!!


There may be 2 problems here with the same symptom - So if you are running Chrome and Mavericks, it could be worth trying.

Bluetooth drivers prevent system from sleeping in Mavericks - what's going on!?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.