Toshiba U400 won't suspend when Bluetooth is enabled

[Neil Broadley]

Binary package hint: bluez

Although the bluetooth module in my Toshiba Satellite Pro U400 is now recognised out of the box (without the need for the Omnibook module), it prevents my laptop from entering suspend. Attempting to enter suspend while the bluetooth is enabled causes a hardlock. Once this occurs, a power down is the only options (CTRL-ALT terminal not responsive, CTRL-ALT-SYSRQ commands not responsive - not even REISUB).

If I click on the indicator applet to disable bluetooth, suspend (and resume) works as it did on Lucid.

This is completely reproducible. There's nothing in /var/log/pm-suspend.log, but I'll attach working and non-working examples nonetheless.

An Ubuntu Forums suggestion to disable NVS saving had no effect (http://ubuntuforums.org/showthread.php?t=1586178&page=5).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluez 4.69-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Oct 11 16:42:38 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: TOSHIBA Satellite Pro U400
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=ba4e6587-4b1a-4642-9f6b-bb14bb3158b9 ro quiet splash acpi_sleep=nonvs
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 07/14/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.10
dmi.board.name: Satellite Pro U400
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.10:bd07/14/2008:svnTOSHIBA:pnSatelliteProU400:pvrPSU45E-005005EN:rvnTOSHIBA:rnSatelliteProU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite Pro U400
dmi.product.version: PSU45E-005005EN
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:03:7A:91:59:03 ACL MTU: 1021:6 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:2028 acl:0 sco:0 events:69 errors:0
  TX bytes:2694 acl:0 sco:0 commands:69 errors:0

[Neil Broadley (scaine)]

I can't get a working suspend anymore - literally just once it worked, now it just hangs again, regardless of Bluetooth. If anyone can help troubleshoot the problem, that would be great. In the meantime, I attach the /var/log/pm-suspend.log I took of a "hung" connection. It doesn't look like it'll be any help.

[Neil Broadley (scaine)]

Recent kernel update (Tuesday 11th Oct 2010) has made a slight improvement. I now get one suspend/resume. All subsequent attempts to suspend thereafter fail with identical symptoms to this initial bug report. If anyone can help troubleshoot this, I'd greatly appreciated it.

[Neil Broadley (scaine)]

Well, I need suspend/resume more than I need my bluetooth mouse, so I've got the following (rubbish) workaround to disable bluetooth :

Edit /etc/modprobe.d/blacklist.conf

Add the following lines at the bottom :
  # Added October 11th 2010
  blacklist toshiba_bluetooth
  blacklist bluetooth

Reboot.

Suspend/Resume is now working, but of course, no bluetooth any more.

I'll maybe try compiling my own Omnibook module as per this ancient article : https://docs.google.com/View?docid=dgd53r6d_36hqmmh4hn. I'm not sure it's even relevant anymore, but whatever - worth a shot.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.