bluetooth doesn't work after suspend/resume

Bug #713577 reported by Ralf Hildebrandt
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)

Bug Description

Binary package hint: bluez

Before suspend, the bluetooth mouse was working flawlessly.
Then I suspended the machine, waited a few seconds and woke it up again.

After that, bluetooth wouldn't work at all.

I'm attaching two log files, hci.log (before suspend up to suspend)
hci2.log (after suspend)

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluetooth 4.87-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Sat Feb 5 11:31:29 2011
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
PackageArchitecture: all
 Socket 0:
   no product info available
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=d3877693-43c0-45cc-821c-6c4dcd692cde ro noquiet nosplash rootfstype=ext4
SourcePackage: bluez 08/20/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.08 FJNB1E3
dmi.board.vendor: FUJITSU
dmi.board.version: CP365186-01
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: P8010
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd08/20/2008:svnFUJITSUSIEMENS:pnLIFEBOOKP8010:pvr:rvnFUJITSU:rnFJNB1E3:rvrCP365186-01:cvnFUJITSUSIEMENS:ct10:cvrP8010: LIFEBOOK P8010
dmi.sys.vendor: FUJITSU SIEMENS
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:03:7A:76:AF:44 ACL MTU: 310:10 SCO MTU: 64:8
  RX bytes:356 acl:0 sco:0 events:13 errors:0
  TX bytes:53 acl:0 sco:0 commands:13 errors:0

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

new hci.log after suspend (supend quits the logging!). Oh, it's empty. I cannot upload an empty file :)

description: updated
Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

I found out that unloading and reloading the "btusb" kernel module makes things work again:

[ 1491.494908] usbcore: deregistering interface driver btusb
[ 1498.093279] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 1498.179653] usbcore: registered new interface driver btusb
[ 1502.661233] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:42/input11
[ 1502.661459] generic-bluetooth 0005:045E:0700.0003: input,hidraw0: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:03:7A:76:AF:44

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

2.6.38-2-generic seems to fix that, at least it hasn't happened (yet)

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

It's back on the very same machine with oneiric and
linux-image-3.0.0-11-generic :(

tags: added: oneiric regression-update
removed: natty
Revision history for this message
tlue (tlueber) wrote :

after resume I get automatic notification that something crashed and to send error report. Also I get the info to do this

sudo hcidump -XYt > $HOME/hci.log

Find attached the hci.log
after a little while things are back running again, but sometimes (after second or third time going to resume) the bluetooth menu (top right) is screwed up and does not give all options anymore like i.e. disconnect form currently connected device or getting to sound settings for that device etc.).

HTH, seems to be a very tricky one

Revision history for this message
Brian Murray (brian-murray) wrote :

I have removed the tag regression-update from this bug report as the tag should be used for a regression which happened when installing a package from the -updates repository. This tag is used by the Stable Release Updates team to watch for regressions in packages from -updates and inappropriate usage of this tag makes it harder to find this category of regression. Thanks for your understanding. To learn more about how we use tags you may want to review

tags: removed: regression-update
Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers