My machine occasionally goes into a state where almost 100% cpu is eaten by syslogd
and blued
. At that time, numerous copies of the following block appear in the console:
4/29/14 10:31:45.000 AM kernel[0]: Item[208]: mID: 216 [0xffffff802ed70000] OpCode 0x0401 (HCI Inquiry) from: blued (40) Asynchronous status: 0x00 (kIOReturnSuccess) state: 1 (WAITING) timeout: 43210
4/29/14 10:31:45.000 AM kernel[0]: mHCIRequestDeleteWasCalled = FALSE
4/29/14 10:31:45.000 AM kernel[0]: expected events = kBluetoothHCIEventCommandStatus
4/29/14 10:31:45.000 AM kernel[0]: expected explicit complete events = kBluetoothHCIEventInquiryComplete
4/29/14 10:31:45.000 AM kernel[0]: possible intermediate events = kBluetoothHCIEventInquiryResult
4/29/14 10:31:45.000 AM kernel[0]: or
4/29/14 10:31:45.000 AM kernel[0]: possible intermediate events = kBluetoothHCIEventInquiryResultWithRSSI
4/29/14 10:31:45.000 AM kernel[0]: or
4/29/14 10:31:45.000 AM kernel[0]: possible intermediate events = kBluetoothHCIEventExtendedInquiryResult
Any ideas what may be causing this and how to resolve?
Best Answer
Blued and syslogd are both daemon processes. Blued is your Bluetooth daemon process and syslogd is is your logging console daemon (crash reported, console log files etc). Blued is connected to your console daemon so I guess that blued is actually the cause of your problem while the syslogd issue is only a result of the blued's problems. Looking at the error it seem that there is an communication error and your blued process is just waiting for a response from a device. The error is that your blued command is your host communicator interface (HCI) and an request is send but without a response. It's weird that blued waiting from the kernel from a response it putting it in a 100% CPU state.
/Library/Preferences/com.apple.bluetooth.plist
~/Library/Preferences/ByHost/com.apple.Bluetooth.*.plist
edit: option 5, it could be caused by cheap and crappy bluetooth hardware connected to your mac of course.