[Gutsy] bluetooth device goes away after suspend or hibernate

Bug #128795 reported by Ted Lemon
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
Invalid
Undecided
Tollef Fog Heen
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I'm running kubuntu gutsy, most recently updated about a half hour ago. Bluetooth works when the system comes up, but after a suspend, kbluetoothd and hciconfig both report that there is no bluetooth device (hci0).

If I try to modprobe -r the bluetooth modules, it fails because they're "in use"; if I do /etc/init.d/bluetooth stop and then modprobe -r rfcomm hidp l2cap hci_usb bluetooth, and then /etc/init.d/bluetooth start, then suddenly hci0 is back, and kbluetoothd reports that a bluetooth device has been plugged in.

Unfortunately, when I put these instructions into /etc/defaults/acpi-support, the kernel reboots instead of suspending.

This is all happening on a first-generation macbook pro.

Revision history for this message
Stefano Rivera (stefanor) wrote :

Confirmed on a 2007 MacBook, running gutsy/amd64

Changed in bluez-utils:
status: New → Confirmed
Changed in linux-source-2.6.22:
status: New → Confirmed
Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :
Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Tollef Fog Heen (tfheen) wrote :

This doesn't look like a bluez-utils problems, so rejecting bluez-utils task. The linux-source-2.6.22 task is still open.

Changed in bluez-utils:
assignee: nobody → tfheen
status: Confirmed → Invalid
Revision history for this message
Alexander Jones (alex-weej) wrote :

still affecting hardy

Revision history for this message
David Huggins-Daines (dhuggins) wrote :

Hi, I'm having this same problem, although it is on a desktop. Hardy/amd64, using a D-Link USB bluetooth module.

It's slightly improved from Gutsy, because on Gutsy, running /etc/init.d/bluetooth restart would not fix it and I had to reboot. On Hardy, this makes the device work again (at least insofar as the gnome-bluetooth icon comes back, and 'hcitool scan' works instead of saying "Device is not available: No such device")

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Has anyone been able to test Intrepid? Does this issue remain? I'm also going to close the linux-source-2.6.22 task as this does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates . The actively developed linux task will remain open. Thanks.

Changed in linux:
status: Confirmed → Incomplete
Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Alexander Jones (alex-weej) wrote : Re: [Bug 128795] Re: [Gutsy] bluetooth device goes away after suspend or hibernate

Remains in intrepid.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Alexander,

Could you do one more test and try the latest pre-release of Jaunty 9.04 (currently Alpha3) - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test suspend via a LiveCD. Thanks.

Revision history for this message
Stefano Rivera (stefanor) wrote :

As far as I can tell, this has been fixed in Jaunty. I don't suffer from it any more.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
BryanFRitt (bryanfritt) wrote :

I found about this file from
http://ubuntuforums.org/archive/index.php/t-944614.html
/usr/lib/pm-utils/sleep.d/20swapctl
You might have to have pm-utils installed for this to work

Upon hibernation, this fixes Bluetooth problem, and might fix an external NTFS partition mount problem(uncomment lines and add mount point, if you want to try it), and having data in swap(the swapon/swapoff lines)[curious as to if adding this swap stuff really helps/hurts, instead of just makes me feel better]

For this I took their code, modified it, and made the file executable, [and used sudo] with the following in it:

#!/bin/bash

#/usr/lib/pm-utils/sleep.d/20swapctl
#MOUNTSPOT='If you choose to add this, Your mount spot goes here'

case "$1" in
hibernate|suspend)
#if mount | grep $MOUNTSPOT -m 1 > /dev/null
#then
# umount $MOUNTSPOT;
#fi
/etc/init.d/bluetooth stop > /dev/null
swapoff -a;
swapon -a;
;;
thaw|resume)
swapoff -a;
swapon -a;
/etc/init.d/bluetooth start > /dev/null
#mount $MOUNTSPOT > /dev/null
;;
*)
;;
esac

Revision history for this message
BryanFRitt (bryanfritt) wrote :

I forgot to say I'm on KUbuntu 8.04.3 64 bit 'Hardy' (if that makes a difference)

Revision history for this message
mikbini (mikbini) wrote :

I just tried Jaunty (fully updated) on a dell mini 9 and this still happens (and the workaround still works).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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