[EeePC 1001 PXD] suspend/resume kills bluetooth

Bug #824144 reported by Jeff Lane 
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fedora
Invalid
Undecided
bluez (Ubuntu)
Fix Released
Medium
Keng-Yu Lin
gnome-bluetooth (Ubuntu)
Invalid
Medium
Unassigned
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Testing Oneiric Alpha 3 with latest updates on the EeePC 1001 PXD. Prior to the suspend test, bluetooth was successfully tested with a bluetooth mouse. At this point, the mouse was connected and usable, and the bluetooth menu showed many items as well as the mouse listed as a device.

After the system was placed into suspend and then resumed, bluetooth no longer functioned. The controller is still present, according to 'hcitool dev' but the mouse will not reconnect, and the menu for bluetooth only shows the entries:

Bluetooth: On (greyed out)
Turn Off Bluetooth
Preferences

If I open Preferences, the Preferences app shows bluetooth as being disabled, contrary to what the indicator is saying. If I try moving the slider over from off to on, it just snaps back to Off again.

The only way to recover Bluetooth I've found is to reboot the system.

I did notice these two lines appear in dmesg output after resume:

[ 1276.640926] btusb 5-1:1.0: no reset_resume for driver btusb?
[ 1276.640937] btusb 5-1:1.1: no reset_resume for driver btusb?

Perhaps that's a clue?

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-8-generic 3.0.0-8.10
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1405 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 46'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,10438437,00100100'
   Controls : 11
   Simple ctrls : 7
Date: Wed Aug 10 15:26:20 2011
HibernationDevice: RESUME=UUID=35f0f71a-9303-4eeb-a6d7-41c1cf4f8824
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
MachineType: ASUSTeK Computer INC. 1001PXD
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=bbe0cd86-364f-4ba4-9c7d-7f9b165d66c1 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-8-generic N/A
 linux-backports-modules-3.0.0-8-generic N/A
 linux-firmware 1.56
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0105
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1001PXD
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0105:bd08/12/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1001PXD
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :

also adding the full syslog

tags: added: blocks-hwcert suspend
tags: added: resume
Ara Pulido (ara)
Changed in linux (Ubuntu):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
importance: Undecided → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Van Hoof (vanhoof) wrote :

Keng-yu -- Can you verify this behaviour on Oneiric A3?

Changed in linux (Ubuntu):
assignee: Canonical Kernel Team (canonical-kernel-team) → Keng-Yü Lin (lexical)
Revision history for this message
Keng-Yu Lin (lexical) wrote :

The only one eeepc approachable is 1015PX. I tested Oneiric with all updates installed. It has the same bug too,

Revision history for this message
Keng-Yu Lin (lexical) wrote :

You can disable and then enable it again. This brings the bluetooth back.

I think the bug is different than what I saw before.

After the resume, the command `hcitool scan` can find the remote discoverable bluetooth devices, which means kernel is working well.

Besides this, after stopping the bluetoothd by `sudo service bluetooth stop`, the applet is not gray.

This is more likely a bug in bluez and/or gnome-bluetooth.

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Changed in bluez (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → Medium
Changed in bluez (Ubuntu):
assignee: nobody → Keng-Yü Lin (lexical)
status: Confirmed → In Progress
Revision history for this message
Keng-Yu Lin (lexical) wrote :

debug log from bluetoothd

Revision history for this message
Keng-Yu Lin (lexical) wrote :

Today's debug finding is a bit interesting.

I installed bluez-dbgsym and add breakpoints in gdb. So in the resume the breakpoints are hit, then I did nothing but continue in gdb. The bluetooth seems to work after the continues.

So now I am suspecting if the cause is the same as bug 812132 I fixed before.

However from the bluetoothd log I do not see the obvious error as in bug 812132. This needs more investigation.

Also tried to apply the patch from bug 812132 on current bluez package. It's not fixing. Could be due to some code changes in bluez?!

Revision history for this message
Keng-Yu Lin (lexical) wrote :

the breakpoints are src/manager.c:manager_find_adapter, src/manager.c:manager_find_adapter_by_id, plugins/hciops.c:device_event.

Revision history for this message
Keng-Yu Lin (lexical) wrote :

Bug 822705 is reported for the bug that bluetooth-applet is not greyed out even if the bluetooth hardware is disabled.

Revision history for this message
Keng-Yu Lin (lexical) wrote :

Can one having the machine test the bluez (4.96-0ubuntu5~kengyu2 ) from https://launchpad.net/~lexical/+archive/bluez/ ?

Changed in bluez (Ubuntu):
status: In Progress → Incomplete
Changed in linux (Ubuntu):
assignee: Keng-Yü Lin (lexical) → nobody
Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-11.18)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.18
Revision history for this message
Keng-Yu Lin (lexical) wrote :

just note I have the feedback (via mail, tested on the machine) that the issue is not seen with the bluez package in comment#10.

Changed in bluez (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Matthew Woerly (nattgew) wrote :

I have a Dell Inspiron 1525 that I just upgraded to Oneiric. I've had the same issue with Bluetooth not working when resuming from suspend. It used to work fine in Natty.
If I do
sudo service bluetooth restart
Then Bluetooth works fine again. I also see the same lines in dmesg:

[ 7343.518981] btusb 7-2.1:1.0: no reset_resume for driver btusb?
[ 7343.518987] btusb 7-2.1:1.1: no reset_resume for driver btusb?

Revision history for this message
Keng-Yu Lin (lexical) wrote :

Copy from https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/823467/comments/15:

The patch is confirmed to fix the issue. I also test on other machines in hands without the issue and it does not cause any malfunction.

Please consider include the attached patch for Oneiric. A binary package is also available in my ppa (https://launchpad.net/~lexical/+archive/bluez)

The issue is block the certification of this bug and bug 824144.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "06-Fix-disabled-after-resume.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
Keng-Yu Lin (lexical) wrote :

Re-sent the patch as an RFC form upstream.

Changed in bluez (Ubuntu):
status: Confirmed → Triaged
status: Triaged → In Progress
Revision history for this message
Keng-Yu Lin (lexical) wrote :

Accepted bluez into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in bluez (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Keng-Yu Lin (lexical) wrote :

bluez 4.96-0ubuntu4 in oneiric-updates should contains the fix. If it's confirmed to fix the eeepc too, we can close the bug too.

Changed in bluez (Ubuntu):
assignee: Keng-Yü Lin (lexical) → Jeff Lane (bladernr)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jeff Lane  (bladernr) wrote :

Marc, can you give the bluez update a try and see if that resolves the bluetooth bug?

Changed in bluez (Ubuntu):
assignee: Jeff Lane (bladernr) → Marc Legris (maaarc)
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Unable to test, our eeepcs were shipped back to the manufacturer

Changed in bluez (Ubuntu):
assignee: Marc Legris (maaarc) → nobody
Revision history for this message
Jacques (jacques-eavr) wrote :

Hi,

I still observe this bug on a 1015PX. Disabling and re-enabling BT after a resume fixes the problem.

Best,
Jacques

Revision history for this message
Jacques (jacques-eavr) wrote :

Sorry, I omitted to mention that I run OO 64 bits with the latest updadtes.

Changed in bluez (Ubuntu):
assignee: nobody → Keng-Yü Lin (lexical)
status: Incomplete → Confirmed
Keng-Yu Lin (lexical)
Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Anthony Wong (anthonywong) wrote :

This machine is now certified with 12.04. This bug should already been fixed.

Changed in bluez (Ubuntu):
status: Incomplete → Fix Released
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Invalid
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.