[Bug 591298] [NEW] Bluetooth stops working after suspend/resume and requires reloading modules/restarting service to work again

Launchpad Bug Tracker 591298 at bugs.launchpad.net
Mon Jul 12 16:41:05 BST 2010


You have been subscribed to a public bug:

HARDWARE:  System is an Alienware M15x.  The device in question is an
Apple Magic Mouse connecting via bluetooth.  I don't have any other
bluetooth devices to test this with...

What happens:
Everything is fine until I suspend the system.  Once I suspend (S3) the system and then resume, bluetooth no longer works properly. 
  *  the bluetooth applet no longer registers any devices (seems like it is not scanning anymore)
  *  hcitool shows no devices
  *  hcitool scan DOES show devices, but I can not connect.
So, after much trial and error, ignoring the problem with bluetooth-applet, I have to remove all the drivers, reinstall the drivers, restart the bluetooth service and THEN I can manually connect via hcitool (but the applet still doesn't show any devices).

So in reality, there are two issues, but the more serious one for now is
the kernel driver issue for bluetooth.

Steps to recreate:
1: Start with running system, bluetooth mouse connected and usable
2: sudo pm-suspend
3: wait a few seconds after suspend and restart the system (I've been doing it automatically for test purposes by echoing a "+60" into /sys/class/rtc/rtc0/wakealarm.
4: after system is fully resumed, check bluetooth applet.  No devices found.
5: from the terminal, hcitool scan to get the address of the mouse
6: hcitool cc <address>; echo $?
7: hcitool auth <address>; echo $?
8: mouse never reconnects.

To work around:
1: after system resumes, service bluetooth stop
2: rmmod the following:
  * hidp
  * rfcomm
  * sco
  * bnep
  * btusb
  * l2cap
  * bluetooth
3: modprobe the following:
  * bluetooth
  * l2cap
  * btusb
  * bnep
  * sco
  * rfcomm
  * hidp
4: service bluetooth restart
5: hcitool scan
6: hcitool cc <address>
7: hcitool auth <address>

and the mouse should start working at this point.  The bluetooth-applet,
however still shows no devices at all.

bladernr at klaatu:~$ lsb_release -d
Description:    Ubuntu 10.04 LTS

bladernr at klaatu:~$ sudo apt-cache policy bluez
bluez:
  Installed: 4.60-0ubuntu8
  Candidate: 4.60-0ubuntu8
  Version table:
 *** 4.60-0ubuntu8 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

bladernr at klaatu:~$ uname -a
Linux klaatu 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  bladernr   2041 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0f20000 irq 22'
   Mixer name	: 'IDT 92HD83C1X5'
   Components	: 'HDA:111d7604,102802a2,00100104'
   Controls      : 16
   Simple ctrls  : 10
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
   Mixer name	: 'Nvidia ID a'
   Components	: 'HDA:10de000a,10de0101,00100100'
   Controls      : 0
   Simple ctrls  : 0
Card1.Amixer.values:
 
Date: Tue Jun  8 10:40:40 2010
HibernationDevice: RESUME=UUID=f4e6db09-5257-40b2-ba2a-0718fc0b3f0d
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Alienware M15x
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 03/11/2010
dmi.bios.vendor: Alienware
dmi.bios.version: A05
dmi.board.vendor: Alienware
dmi.board.version: A05
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A05
dmi.modalias: dmi:bvnAlienware:bvrA05:bd03/11/2010:svnAlienware:pnM15x:pvrA05:rvnAlienware:rn:rvrA05:cvnAlienware:ct8:cvrA05:
dmi.product.name: M15x
dmi.product.version: A05
dmi.sys.vendor: Alienware

** Affects: gnome-bluetooth (Ubuntu)
     Importance: Medium
         Status: Triaged


** Tags: amd64 apport-bug kernel-input kernel-needs-review kernel-power kernel-suspend kj-triage lucid resume suspend
-- 
Bluetooth stops working after suspend/resume and requires reloading modules/restarting service to work again
https://bugs.edge.launchpad.net/bugs/591298
You received this bug notification because you are a member of Bluetooth, which is subscribed to gnome-bluetooth in ubuntu.



More information about the Ubuntu-bluetooth mailing list