[Lenovo ThinkPad Twist] Bluetooth subsystem dies after suspend

[Till Kamppeter]

I am using Saucy in XMir mode with the standard Unity desktop on the Lenovo Thinkpad Twist.

When I suspend the system not only the suspend itself is broken (bug 1213233) but also after waking up I cannot use my Bluetooth devices any more (mouse, keyboard). I have to reboot to get Bluetooth back working.

Do not ask me to update the BIOS from 1.52 to 1.57, this leads to bug 1210748.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: till 3099 F.... pulseaudio
Date: Fri Aug 16 22:19:52 2013
HibernationDevice: RESUME=UUID=e0af6e5c-3cf3-47e2-8603-6a9ffb019484
InstallationDate: Installed on 2013-06-05 (72 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605)
MachineType: LENOVO 334729G
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=80d8eb01-b0c3-47cc-8dba-1ed122b2be4f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-2-generic N/A
 linux-backports-modules-3.11.0-2-generic N/A
 linux-firmware 1.113
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GDET92WW (1.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 334729G
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGDET92WW(1.52):bd02/05/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 334729G
dmi.product.version: ThinkPad Twist
dmi.sys.vendor: LENOVO

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Till Kamppeter (till-kamppeter)]

This is independent whether the Unity desktop is run with XMir or normal X.

I did not use Suspend for very long time, can even be the first time for me with Saucy on this machine.

[Till Kamppeter (till-kamppeter)]

Sometimes, the Bluetooth devices, sometime only one of them, work again after suspend, but in most cases they are dead.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test some earlier kernels, to see if this is a regression? It might be good to start with the 3.8, 3.9 and 3.10 kernels:

v3.8: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/
v3.9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/
v3.10: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/

You don't have to perform a re-install, you can install these kernels on top of your existing installation, then select them from the GRUB menu during boot.

[Till Kamppeter (till-kamppeter)]

I get the problem only with the 3.11.x kernel. All the old (3.10.x and earlier) kernels are OK.

[Joseph Salisbury (jsalisbury)]

Thanks for testing, Till.

I'd next try to identify which 3.11 release candidate introduced the regression.

Can you test the following kernels and report back? We are looking for the earliest kernel version that exhibits this bug:

v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy
v3.11-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy
v3.11-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/
v3.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

[Till Kamppeter (till-kamppeter)]

Since I have tried the kernels 3.8, 3.9, and 3.10 yesterday, I am not able to reproduce the bug any more, even not with the current Ubuntu kernel (3.11.0-3-generic) and the previous one (3.11.0-2-generic). Also the problem of suspend automatically waking up immediately again (bug 1213233) does not occur any more.

All tests done in XMir mode.

[Joseph Salisbury (jsalisbury)]

Ok, thanks for the update, Till. I'll keep this bug as incomplete for now. Please move it back to confirmed if the bug starts to happen again.

[Hans de Goede (j-w-r-degoede)]

Hi all,

I just hit the same problem, and I've managed to fix it for my case (Dell E6430 laptop with integrated bluetooth).

I've had exactly the same experience as Till, in that 3.11 caused bt to no longer work after a suspend/resume for me. I'm surprised to hear that the problem has magically gone away for Till, as there is a very real reason causing it in the form of a "fix" in 3.11 .

I've written a patch for this (reverting the fix) and send it upstream. I'll also attach it here.

Regards,

Hans

[Francisco Cribari (cribari)]

I am having this problem on a DELL XPS 13 which runs on Ubuntu Gnome 13.10. I did not have the problem prior to upgrading to version 13.10. I am running kernel 3.11.0-12-generic .

[omriasta (omriasta)]

Also have this problem running Ubuntu 13.10 kernel 3.11.0-12-generic on Lenovo X1 Carbon and Microsoft BT mouse 5000. Never had an issue before with this hardware.
Also noticed, when resuming from suspend and opening the bluetooth dialog, I tried to turn bluetooth off and on again. The dialog will not re-enable bluetooth (it goes on and switches off by itself immediately). Reboot did not resolve it, had to do a full shutdown and then turn back on to get bluetooth working again.
lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 5986:0266 Acer, Inc
Bus 001 Device 005: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 001 Device 003: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bdb:1926 Ericsson Business Mobile Networks BV
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[gpothier (gpothier)]

I did some testing with the 13.10 release version:
Kernel 3.10: works fine
Kernel 3.11-rc1: fails

I marked the bug as confirmed as per Joseph's instructions.

I've seen similar bug reports on other distros, it seems something got broken in kernel 3.11.

[Hans de Goede (j-w-r-degoede)]

As I already mentioned in comment #11 I've a patch fixing this, see comment #11.

[Hans de Goede (j-w-r-degoede)]

p.s. note that the patch in question has already been merged into 3.12-rc4

[Ing. Radomír Polách (exander77)]

I am suffering from this bug too, could you introduce a fix as soon as possible. It is highly lowering the usability of the system. After resume I had to restart, because bluetooth doesn't work and and network doesn't work either, because of this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262.

[Joseph Salisbury (jsalisbury)]

@Hans, thanks for the patch. However, I don't see the patch in the mainline tree as of yet. Do you happen to know the SHA1 for the commit in mainline?

[Hans de Goede (j-w-r-degoede)]

@Joseph,

I'm sorry I was wrong it is not upstream yet. I was on the wrong git branch when I checked. It has been accepted into bluetooth.git:
http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git

But it has not found its way into Linus' tree yet.

Regards,

Hans

[omriasta (omriasta)]

@Hans, any way to apply the patch without waiting for kernel 3.12 or compiling the entire kernel?

[Hans de Goede (j-w-r-degoede)]

@omriasta, no I'm afraid not.

[Benoit Grégoire (benoitg)]

I also get this bug since upgrading to saucy. While waiting for the kernel fix, the workaround here does work for this bug as well: http://ubuntuforums.org/showthread.php?t=1387211

[penalvch (penalvch)]

Till Kamppeter, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (1.63). Via 1.58, this version would have an internal mouse fix for 1.57 . If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything regarding bluetooth suspension? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[gpothier (gpothier)]

Christopher, this bug is not specific to the Lenovo ThinkPad Twist. In this bug report it affects users on a Lenovo X1 Carbon, two different Dell laptops, and in my case an HP Folio 13. There are also similar bug reports in other distros that point to a regression in the 3.11 kernel.

[gpothier (gpothier)]

Done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256747

[Jeffrey Flaker (jflaker)]

I've been having this issue also. After a conversation in #ubuntu on IRC, someone pointed out a script for /etc/pm/sleep.d

The script as shown below seems to have fixed this issue, although it is (at least to me) a workaround.

Thanks
_______________________________
#!/bin/bash
#Code from http://ubuntuforums.org/showthread.php?t=1387211

. /usr/lib/pm-utils/functions

case "$1" in
    hibernate|suspend)
    rfkill block bluetooth
    ;;
    thaw|resume)
    rfkill unblock bluetooth
    rmmod btusb
    modprobe btusb
    ;;
    *)
    ;;
esac

exit

[Jeffrey Flaker (jflaker)]

Further note....The script seems to work for others also, not just thinkpad.

[Jeffrey Flaker (jflaker)]

http://ubuntuforums.org/archive/index.php/t-1387211.html

[penalvch (penalvch)]

Jeffrey Flaker, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jeffrey Flaker (jflaker)]

I filed the bug under

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280911

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]