bluetooth doesn't work after suspend / resume on dell vostro 1310

Bug #764536 reported by u-foka
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Medium
AceLan Kao
Natty
Fix Released
Medium
AceLan Kao
Oneiric
Fix Released
Medium
AceLan Kao

Bug Description

Binary package hint: bluez

Hy!

When I start up my laptop, bluetooth works fine, but after suspend / resume itstops working... The bluetooth applet is grayed, and empty, but the menu says: "Bluetooth: on" and "Turn off bluetooth"

After I run "sudo service bluetooth restart" it works fine again.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 18 14:07:27 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110327)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Dell Inc. Vostro1310
ProcEnviron:
 LC_TIME=hu_HU.UTF-8
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=019bae9d-0699-4120-aa8a-3feed7bd6132 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0G930C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1310:pvrNull:rvnDellInc.:rn0G930C:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1310
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:21:86:46:A7:F0 ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING
  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
u-foka (ufooka) wrote :
Revision history for this message
u-foka (ufooka) wrote :

I was tryed to produce the hci.log apport suggested, and discovered two things:
After resume, hcidump tells me that "device: disconnected", and appearently the device itself works, or at least "hcitool scan" lists nearby devices. So the problem should be with the gui.

Revision history for this message
introspectif (muhammadhirman) wrote :

This affects me on my MacBook too. My Apple bluetooth keyboard ceases to work after a suspend. The only solution is to "sudo service restart bluetooth".

How can I help?

Revision history for this message
Dmitry K (dkekel) wrote :

Same on MSI X-Slim 340. Just upgraded to 11.04 yesterday evening.
After suspend bluetooth applet is gray, service bluetooth restart brings it back to the working state.

Revision history for this message
AceLan Kao (acelankao) wrote :

u-foka,

Could you help to try if this kernel fix the problem?
Thanks.
http://people.canonical.com/~acelan/bugs/lp764536/

And for others,
I might need your bt's usbid to fix the problem if the kernel fix u-foka's problem.

Revision history for this message
u-foka (ufooka) wrote :

Hy!

This kernel solved the problem!

But I discovered an other: When I suspend with bluetooth of (from the bt menu) when I resume, I can't enable bluetooth until I restart the bluetooth service. This also happens on my GF's Lenovo S10-2 with the original natty kernel.
Should I report this separately?

Thanks for the fix!

Revision history for this message
AceLan Kao (acelankao) wrote :

u-foka,

Glad to hear that works for you, I might know what happened in the kernel.
As you might know, there are many bt devices have the same symptom as yours, and the kernel I provided above only works for your h/w, I have to find out a better solution for all other h/w and it takes time.

And yes, you have to file another new bug for the new problem, but please postpone it if you encounter the new problem only with the new kernel. I'll submit a SRU to the Ubuntu kernel to fix the problem and after that you can file the new bug.

Revision history for this message
u-foka (ufooka) wrote :

Hy!

There are two seems different problems with the current release kernel:
1: when I suspend with bt enabled, then bt icon is useless after resume (but hcitool seems to work, this was fixed by your kernel)
2: when I suspend with bt DISABLED, then bt icon is useless after resume the bluetooth chip is disabled so not even hcitool works, because I can't enable bt with the icon.

The second problem exists with the release and the patched kernel too, but I didn't found the difference before I tested with the patched kernel.

Also when I discovered the second problem, I checked if the Lenovo s10-2 has the same problem (I did that for the first before it was reported, but it was ok) and this second problem exists on that machine too.

So it seems that the second problem, while seems simlar, not related to the first at all. (At least from the users pov :)

Revision history for this message
David Chen (david.chen) wrote :

Same problem on this device:

Bus 005 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Revision history for this message
AceLan Kao (acelankao) wrote :

u-foka, David,

I update a new kernel in the same url, I think it should suitable for all bt devices, please git it a try.

u-foka,

I totally understand the second issue, and I can reproduce here, but I don't have any idea for it now.

Revision history for this message
u-foka (ufooka) wrote :

Hy!

The new kernel still works as expected :)

Revision history for this message
JanisA (janis-adati) wrote :

On my MSI X-Slim 340 there is no difference bluetooth dosen't work after suspend and if system is started after full power off bluetooth isn't working the same. To get it back working i have to restart bluetooth service and after that click on bluetooth icon to turn it off and then back on. Only then it works :(

Revision history for this message
AceLan Kao (acelankao) wrote :

u-foka,

Great, thanks for the testing.

JanisA,

Could you give me your bt usbid, it will be shown by the command "lsusb", thanks.

Revision history for this message
David Chen (david.chen) wrote :

@Acelan, this one has the problem as well:

Bus 002 Device 005: ID 0cf3:3002 Atheros Communications, Inc.

Revision history for this message
u-foka (ufooka) wrote :

Hy!

Any news on this?

Chris Van Hoof (vanhoof)
Changed in bluez (Ubuntu):
assignee: nobody → AceLan Kao (acelankao)
importance: Undecided → Medium
status: New → In Progress
tags: added: hwe-blocker
Revision history for this message
AceLan Kao (acelankao) wrote :

u-foka,

Yes, this problem will be fixed in the next kernel release, the version should be 2.6.38-8.43 or 2.6.38-9.43 if the ABI bumped.

David, JanisA,

Could you file new bugs for your problems, I think there might be some different issue in your cases.
Thanks.

Changed in bluez (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Chris Van Hoof (vanhoof) wrote :

Closing this task as Fix Released as 2.6.38-10 has been released

Changed in bluez (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
ej3416 (jensehl) wrote :

2.6.38-10 still has this problem on my PC.

Revision history for this message
AceLan Kao (acelankao) wrote :

jensehl,

Could you post more detail here?
I think maybe you have encountered another issue and have to file another new bug on launchpad.

Chris Van Hoof (vanhoof)
Changed in bluez (Ubuntu Natty):
status: New → Fix Released
importance: Undecided → Medium
assignee: nobody → AceLan Kao (acelankao)
Revision history for this message
Ricardo Graça (devius) wrote :

This problem recently appeared on my system. It used to work fine with all kernel versions that were available on Natty, but since I've upgraded to Oneiric beta my bluetooth mouse doesn't work anymore after resuming from suspend. The strange thing is that the panel indicator show as if bluetooth is connected and the only way to get my mouse working again is to disable bluetooth and enable it again. System is an Asus Eee PC 1000H running kernel 3.0.0-11 and the bluetooth adapter appears to be a device ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1.
Should I file a new bug for this bluetooth adapter?

Revision history for this message
AceLan Kao (acelankao) wrote :

Devius,

Yes, you should file a new bug for your problem, since the bt chip is different and kernel is not the same as well.

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

Other bug subscribers

Remote bug watches

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