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

The only problem with that, is that the macbook will go into hibernation mode after 12 minutes when on battery...not really practical, and more of a pain in the butt than waiting for it to go to sleep and having the instant wakeup. Thanks though!

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?

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.

The problem is that this bug prevents sleep using the energy saver settings, which is a problem for those of us who want our computers to go to sleep when unattended.

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

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)

I shall bump this until we get an answer from Apple.

My 2 MBP are affected (15" and 13"), both have been freshly reformatted. It has to be a bug in Mavericks.

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.

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.

I have the sam problem, same log. Annoying!!

It seems it's AirPort and Bluetooth that take some 40 seconds to react.

Same pb for me here, on a Mid 2010 MacBook Pro, with a clean install of Mavericks. Same log with pmset -g assertions.

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.

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.

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.