502527 – Bluetooth doesn't wake up after suspending to RAM

Bug 502527 - Bluetooth doesn't wake up after suspending to RAM

Summary: Bluetooth doesn't wake up after suspending to RAM

Status:	RESOLVED WONTFIX

Alias:	None

Product:	openSUSE 11.1
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 11.1

Priority:	P5 - None Severity: Normal with 1 vote (vote)
Target Milestone:	---
Assignee:	Forgotten User ZhJd0F0L3x
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2009-05-09 10:48 UTC by Ladislav Nesnera
Modified:	2009-07-22 06:12 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
/var/log/pm-suspend.log (9.07 KB, text/plain) 2009-05-09 10:48 UTC, Ladislav Nesnera	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ladislav Nesnera 2009-05-09 10:48:10 UTC

Created attachment 291176 [details]
/var/log/pm-suspend.log

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4) Gecko/20090426 SUSE/3.5b4-3.1 Firefox/3.5b4

I used pm-suspend command. After computer wake up bluetooh LED stays off and device doesn't work. WiFi works fine.

/var/run/pm-suspend contains:
export KERNEL_LOGLEVEL=1
export cpu0_governor_STATE=ondemand
export cpu1_governor_STATE=ondemand

uname -r
2.6.27.21-0.1-default

s2ram -n
Machine matched entry 566:
    sys_vendor   = 'LENOVO'
    sys_product  = ''
    sys_version  = 'ThinkPad T60'
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "LENOVO"
    sys_product  = "1951FEG"
    sys_version  = "ThinkPad T60"
    bios_version = "79ETD7WW (2.17 )"


Reproducible: Always

Comment 1 Forgotten User ZhJd0F0L3x 2009-06-16 10:36:49 UTC

Can you still toggle bluetooth with the Fn-hotkey after resuming?

what are the contents of /proc/acpi/ibm/bluetooth?

Comment 2 Axel Braun 2009-07-17 08:33:27 UTC

I'm struggeling with the same problem.

s2ram -n
Machine matched entry 440:
    sys_vendor   = 'IBM'
    sys_product  = '2529*'
    sys_version  = ''
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "IBM"
    sys_product  = "2529FKG"
    sys_version  = "ThinkPad Z60m"
    bios_version = "77ET54WW (1.14 )"

With Fn-F5 I can toggle the bluetooth settings.
Before:
cat /proc/acpi/ibm/bluetooth
status:         disabled                         
commands:       enable, disable    

After:
cat /proc/acpi/ibm/bluetooth
status:         enabled                          
commands:       enable, disable   

After toggeling I can see it  from my Palm and transfer data.
Looks like a glitch in the resume script?

Comment 3 Holger Macht 2009-07-20 09:16:36 UTC

This is an issue with the thinkpad_acpi driver which stored the state of the bluetooth killswich in nvram to read it on resume and set the correct state. You should see the same issue with booting, bluetooth disabled -> reboot -> bluetooth enabled. There was another bugreport about this issue which came in too late in the release cycle so that a patch was considered to intrusive to be put into the kernel at this point in time.

So if you can change toggle the bluetooth settings with Fn-F5 and so get bluetooth working again, I consider this issue as not too bad. Sorry, this won't get fixed for 11.1, but should be for openSUSE Factory or 11.2.

Comment 4 Ladislav Nesnera 2009-07-21 12:44:41 UTC

Thank you for explanation. I learned to use the Fn+F5 ;?)

Comment 5 Axel Braun 2009-07-22 06:12:19 UTC

Can we verify that it still does not work in 11.2, or will you reassign the bug for 11.2? My testing machine for 11.2 does not have bluetooth...