Arch Linux

quantumphaze

Member

From: Melbourne, Australia

Registered: 2008-11-14

Posts: 175

Bluetoothd stops working after suspend/resume

After resuming from RAM the bluetooth subsystem stops working. I don't know if this is somehow related to the bluetoothd using 100% CPU problem two months ago which also effected me. The only difference between then and now is that it no longer takes 100% CPU but still remains dead.

Restarting the bluetoothd daemon fixes the problem then and there, but it's not the correct solution. Is anyone else suffering this same problem?

If I use the physical switch on the laptop it show similar lines in the log but recovers.

grep bluetoothd /var/log/daemon.log

### After resume (nothing since boot time before here) ###

Sep  8 15:38:17 localhost bluetoothd[4674]: HCI dev 0 down
Sep  8 15:38:17 localhost bluetoothd[4674]: Adapter /org/bluez/4674/hci0 has been disabled
Sep  8 15:38:17 localhost bluetoothd[4674]: HCI dev 0 unregistered
Sep  8 15:38:17 localhost bluetoothd[4674]: Stopping hci0 event socket
Sep  8 15:38:17 localhost bluetoothd[4674]: Unregister path: /org/bluez/4674/hci0
Sep  8 15:38:17 localhost bluetoothd[4674]: HCI dev 0 registered
Sep  8 15:38:17 localhost bluetoothd[4674]: Listening for HCI events on hci0
Sep  8 15:38:17 localhost bluetoothd[4674]: HCI dev 0 up

### Restarted bluetoothd here ###

Sep  8 15:38:33 localhost bluetoothd[4674]: Stopping hci0 event socket
Sep  8 15:38:33 localhost bluetoothd[4674]: Stopping SDP server
Sep  8 15:38:33 localhost bluetoothd[4674]: Exit
Sep  8 15:38:34 localhost bluetoothd[6843]: Bluetooth daemon 4.96
Sep  8 15:38:34 localhost bluetoothd[6843]: Starting SDP server
Sep  8 15:38:34 localhost bluetoothd[6843]: Listening for HCI events on hci0
Sep  8 15:38:34 localhost bluetoothd[6843]: HCI dev 0 up
Sep  8 15:38:34 localhost bluetoothd[6843]: input-headset driver probe failed for device 5C:57:C8:F6:28:9B
Sep  8 15:38:34 localhost bluetoothd[6843]: input-headset driver probe failed for device 18:14:56:7A:E4:50
Sep  8 15:38:34 localhost bluetoothd[6843]: Adapter /org/bluez/6843/hci0 has been enabled
Sep  8 15:38:34 localhost bluetoothd[6843]: Inquiry Cancel Failed with status 0x12

### Toggled the physical switch ###

Sep  8 15:54:07 localhost bluetoothd[6843]: HCI dev 0 down
Sep  8 15:54:07 localhost bluetoothd[6843]: Adapter /org/bluez/6843/hci0 has been disabled
Sep  8 15:54:08 localhost bluetoothd[6843]: HCI dev 0 unregistered
Sep  8 15:54:08 localhost bluetoothd[6843]: Stopping hci0 event socket
Sep  8 15:54:08 localhost bluetoothd[6843]: Unregister path: /org/bluez/6843/hci0
Sep  8 15:54:17 localhost bluetoothd[6843]: HCI dev 0 registered
Sep  8 15:54:17 localhost bluetoothd[6843]: Listening for HCI events on hci0
Sep  8 15:54:17 localhost bluetoothd[6843]: HCI dev 0 up
Sep  8 15:54:17 localhost bluetoothd[6843]: input-headset driver probe failed for device 5C:57:C8:F6:28:9B
Sep  8 15:54:17 localhost bluetoothd[6843]: input-headset driver probe failed for device 18:14:56:7A:E4:50
Sep  8 15:54:17 localhost bluetoothd[6843]: Adapter /org/bluez/6843/hci0 has been enabled

I just want to know if this is just me or everyone.

---

▁▂▃▄▅▆▇█▉▊▋▌▍▎▏▏▎▍▌▋▊▉█▇▆▅▄▃▂▁

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Bluetoothd stops working after suspend/resume

Check /var/log/messages.log, might be that bluetoothd gets into trouble because D-Bus isn't fully started yet. Happens here.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy