Package: bluez Version: 4.94-3 Followup-For: Bug #632960 I'm seeing the same problem resuming from suspend only for me, the bluetooth may work 1 out of 10 resumes.
The only way I can restore bluetooth after a suspend is to restart the bluetooth daemon or unplug/replug the usb dongle. Here is the output when I plug in the device: [87025.252078] usb 6-1: new full speed USB device number 12 using uhci_hcd [87025.314115] usb 6-1: New USB device found, idVendor=047d, idProduct=105e [87025.314124] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [87025.314132] usb 6-1: Product: BCM92045B3 ROM [87025.314137] usb 6-1: Manufacturer: Broadcom Corp [87025.314143] usb 6-1: SerialNumber: 00191566A46A Here is a section from my /var/log/daemon.log when the bluetooth fails to work post resume. Sep 7 11:40:40 user-laptop acpid: client 1617[0:0] has disconnected Sep 7 11:40:40 user-laptop bluetoothd[14430]: HCI dev 0 down Sep 7 11:40:40 user-laptop bluetoothd[14430]: Adapter /org/bluez/14430/hci0 has been disabled Sep 7 11:40:40 user-laptop bluetoothd[14430]: HCI dev 0 unregistered Sep 7 11:40:40 user-laptop bluetoothd[14430]: Stopping hci0 event socket Sep 7 11:40:40 user-laptop bluetoothd[14430]: Unregister path: /org/bluez/14430/hci0 Sep 7 11:40:40 user-laptop bluetoothd[14430]: HCI dev 0 registered Sep 7 11:40:40 user-laptop bluetoothd[14430]: Listening for HCI events on hci0 Sep 7 11:40:40 user-laptop bluetoothd[14430]: HCI dev 0 up Sep 7 11:40:40 user-laptop acpid: client connected from 1617[0:0] Sep 7 11:40:40 user-laptop acpid: 1 client rule loaded Sep 7 11:40:44 user-laptop dhclient: receive_packet failed on wlan0: Network is down Sep 7 11:40:44 user-laptop dhclient: receive_packet failed on wlan0: Network is down Sep 7 11:40:48 user-laptop nmbd[1709]: [2011/09/07 11:40:48.152484, 0] lib/interface.c:542(load_interfaces) Sep 7 11:40:48 user-laptop nmbd[1709]: WARNING: no network interfaces found Here is working bluetooth post resume Sep 7 22:56:34 user-laptop acpid: client 1617[0:0] has disconnected Sep 7 22:56:34 user-laptop bluetoothd[14430]: HCI dev 0 down Sep 7 22:56:34 user-laptop bluetoothd[14430]: Adapter /org/bluez/14430/hci0 has been disabled Sep 7 22:56:34 user-laptop bluetoothd[14430]: HCI dev 0 unregistered Sep 7 22:56:34 user-laptop bluetoothd[14430]: Stopping hci0 event socket Sep 7 22:56:34 user-laptop bluetoothd[14430]: Unregister path: /org/bluez/14430/hci0 Sep 7 22:56:34 user-laptop bluetoothd[14430]: HCI dev 0 registered Sep 7 22:56:34 user-laptop bluetoothd[14430]: Listening for HCI events on hci0 Sep 7 22:56:34 user-laptop bluetoothd[14430]: HCI dev 0 up Sep 7 22:56:34 user-laptop bluetoothd[14430]: input-headset driver probe failed for device 5C:17:D3:EA:73:B6 Sep 7 22:56:34 user-laptop bluetoothd[14430]: Adapter /org/bluez/14430/hci0 has been enabled Sep 7 22:56:34 user-laptop acpid: client connected from 1617[0:0] Sep 7 22:56:34 user-laptop acpid: 1 client rule loaded Sep 7 22:56:38 user-laptop dhclient: receive_packet failed on wlan0: Network is down Sep 7 22:56:38 user-laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.254 port 67 Sep 7 22:56:38 user-laptop dhclient: send_packet: Network is unreachable Sep 7 22:56:38 user-laptop dhclient: send_packet: please consult README file regarding broadcast address. Sep 7 22:56:39 user-laptop dhclient: receive_packet failed on wlan0: Network is down Sep 7 22:56:42 user-laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.254 port 67 Sep 7 22:56:42 user-laptop dhclient: send_packet: Network is unreachable Sep 7 22:56:42 user-laptop dhclient: send_packet: please consult README file regarding broadcast address. Sep 7 22:56:53 user-laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.254 port 67 Sep 7 22:56:55 user-laptop dhclient: DHCPACK from 192.168.1.254 Sep 7 22:56:55 user-laptop dhclient: bound to 192.168.1.65 -- renewal in 34710 seconds. The line "Adapter /org/bluez/14430/hci0 has been enabled" seems to be the indication that the bluetooth adapter will work post resume. Perhaps this is a dbus issue? I can do more testing if needed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.4.14-1 simple interprocess messaging syst ii libbluetooth3 4.94-3 Library to use the BlueZ Linux Blu ii libc6 2.13-16 Embedded GNU C Library: Shared lib ii libcap-ng0 0.6.6-1 An alternate POSIX capabilities li ii libdbus-1-3 1.4.14-1 simple interprocess messaging syst ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libudev0 172-1 libudev shared library ii libusb-0.1-4 2:0.1.12-19 userspace USB programming library ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii module-init-tools 3.16-1 tools for managing Linux kernel mo ii python-dbus 0.84.0-2 simple interprocess messaging syst ii python-gobject 2.28.6-4 Python bindings for the GObject li ii udev 172-1 /dev/ and hotplug management daemo bluez recommends no packages. bluez suggests no packages. -- Configuration Files: /etc/default/bluetooth changed: BLUETOOTH_ENABLED=1 HID2HCI_ENABLED=1 HID2HCI_UNDO=0 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
