RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,058
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
no bt after sleep
I think in some cases the native BT drivers will try to start BT before the firmware is loaded...
As per this post I tried reseating the BT module.
https://discussions.apple.com/message/18950593#18950593
After repeated wakeups I still have BT working.
But I did notice a few times where it turned to Not Available and active again. When I check the log I saw this
Code:Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x6800 **** Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0x6800 **** Nov 17 23:38:44 MacBook-Pro kernel[0]: [IOBluetoothFamily][staticBluetoothTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x6800 Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [IOBluetoothHostControllerUSBTransport][StartInterruptPipeRead] -- mInt0InterruptPipe->clearStall (true) failed with error 0xE0005000 (kUSBHostReturnPipeStalled) -- 0x6800 **** Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [IOBluetoothHostControllerUSBTransport][InitializeTransportWL] -- failed -- calling DoDeviceReset (kBluetoothControllerReEnumerateModule) -- 0x6800 **** Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- Re-Enumeration is currently not permitted -- this = 0x6800 **** Nov 17 23:38:44 MacBook-Pro kernel[0]: **** [IOBluetoothFamily][ProcessBluetoothTransportShowsUpActionWL] -- Error!! -- Something went wrong in the setup process. Could not communicate with Bluetooth Transport successfully -- 0x4a00 -- 0x6800 **** Nov 17 23:38:44 MacBook-Pro blued[87]: Host controller terminated Nov 17 23:38:44 MacBook-Pro kernel[0]: AirPort: RSN handshake complete on en1 Nov 17 23:38:44 MacBook-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.2 starting on OS X Darwin 15.0. Nov 17 23:38:44 MacBook-Pro kernel[0]: BrcmPatchRAM2: [13d3:3404]: USB [28C2DD40122E v274] "BCM20702A0" by "Broadcom Corp" Nov 17 23:38:44 MacBook-Pro networkd[286]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID Nov 17 23:38:45 --- last message repeated 3 times --- Nov 17 23:38:45 MacBook-Pro kernel[0]: BrcmPatchRAM2: [13d3:3404]: Firmware upgrade completed successfully. Nov 17 23:38:45 MacBook-Pro kernel[0]: BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". Nov 17 23:38:45 MacBook-Pro kernel[0]: BrcmPatchRAM2: Processing time 0.516 seconds. Nov 17 23:38:45 MacBook-Pro kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0xd000 **** Nov 17 23:38:45 MacBook-Pro kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0xd000 **** Nov 17 23:38:45 MacBook-Pro kernel[0]: [IOBluetoothFamily][staticBluetoothTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0xd000 Nov 17 23:38:45 MacBook-Pro wirelessproxd[76]: Peripheral manager is not powered on Nov 17 23:38:45 MacBook-Pro kernel[0]: [IOBluetoothHostController::setConfigState] calling registerService Nov 17 23:38:45 MacBook-Pro kernel[0]: **** [IOBluetoothFamily][ProcessBluetoothTransportShowsUpActionWL] -- calling IOBluetoothFamily's registerService() -- 0xf8e0 -- 0x4a00 -- 0xd000 **** Nov 17 23:38:45 MacBook-Pro kernel[0]: **** [IOBluetoothFamily][ProcessBluetoothTransportShowsUpActionWL] -- Connected to the transport successfully -- 0xf8e0 -- 0x4a00 -- 0xd000 ****
I think in some cases the native BT drivers will try to start BT before the firmware is loaded...