Bluetooth fails after suspend/resume with bluez 4.95

Bug #818243 reported by Michael Marley
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Mathieu Trudel-Lapierre

Bug Description

After updating to bluez 4.95 on my Oneiric x86_64 system, bluetooth no longer works after a suspend/resume cycle. Additionally, the suspend/resume cycle also sometimes causes "bluetoothd" to spin, taking up 100% of a CPU core until I kill it. Doing a "sudo service bluetooth restart" causes bluetooth to begin working again. Reverting to 4.94 also causes the problem to go away.

I have included an lsusb from my system. If I should provide any more data, please let me know.

Revision history for this message
Michael Marley (mamarley) wrote :
Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try if that's still an issue with 4.96? Mathieu could you check if you get that as well? We should make sure it's just not broken with the update

Changed in bluez (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Well, from the look of things it's probably broken by the hid2hci udev rule for S3 resume. To make sure (and to figure out how we can fix it); could you please attach the output of the udev log and reproduce a suspend/resume cycle?

To get the udev logs:

/sbin/udevadm monitor

This will show all udev events in output, until killed of with Control-C or something, so it will log things across a suspend/resume.

Thanks in advance!

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still get the issue? could you reply to the comment?

Revision history for this message
Michael Marley (mamarley) wrote :

Oh, sorry. I must have missed the last notification. The problem is gone now.

Changed in bluez (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :

This happens on my raring install.

Running /etc/init.d/bluetooth stop && /etc/init.d/bluetooth start after a resume brings it back.

usb-devices says I have a
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=8197 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0

Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :
Download full text (3.8 KiB)

udev logs :
falken@wopr:~/Documents$ sudo /sbin/udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[4742.108418] change /devices/platform/regulatory.0 (platform)
UDEV [4742.115153] change /devices/platform/regulatory.0 (platform)
KERNEL[4749.051430] remove /devices/system/machinecheck/machinecheck1 (machinecheck)
UDEV [4749.051495] remove /devices/system/machinecheck/machinecheck2 (machinecheck)
KERNEL[4749.051538] remove /devices/system/machinecheck/machinecheck2 (machinecheck)
UDEV [4749.051578] remove /devices/system/machinecheck/machinecheck1 (machinecheck)
KERNEL[4749.051617] remove /devices/system/machinecheck/machinecheck3 (machinecheck)
KERNEL[4749.051652] add /devices/system/machinecheck/machinecheck1 (machinecheck)
KERNEL[4749.051688] add /devices/system/machinecheck/machinecheck2 (machinecheck)
KERNEL[4749.051728] add /devices/system/machinecheck/machinecheck3 (machinecheck)
KERNEL[4749.051811] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
KERNEL[4749.051869] add /devices/virtual/watchdog/watchdog3 (watchdog)
KERNEL[4749.051920] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/rfkill4 (rfkill)
KERNEL[4749.051968] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0 (bluetooth)
KERNEL[4749.052070] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0 (bluetooth)
KERNEL[4749.052125] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/rfkill5 (rfkill)
UDEV [4749.052172] add /devices/system/machinecheck/machinecheck2 (machinecheck)
UDEV [4749.060130] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
KERNEL[4749.060236] remove /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
UDEV [4749.060318] remove /devices/system/machinecheck/machinecheck3 (machinecheck)
KERNEL[4749.060403] add /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
UDEV [4749.060462] add /devices/system/machinecheck/machinecheck3 (machinecheck)
KERNEL[4749.060540] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
UDEV [4749.060599] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/rfkill4 (rfkill)
UDEV [4749.060690] remove /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
UDEV [4749.060746] add /devices/virtual/watchdog/watchdog3 (watchdog)
UDEV [4749.060798] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0 (bluetooth)
UDEV [4749.060851] add /devices/system/machinecheck/machinecheck1 (machinecheck)
UDEV [4749.060901] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0 (bluetooth)
UDEV [4749.063161] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/rfkill5 (rfkill)
UDEV [4749.073069] add /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_...


Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.