Bug 198753 - [X86_64] STR: system wakes up immediately after suspend
Summary: [X86_64] STR: system wakes up immediately after suspend
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-11 12:45 UTC by Peter Weber
Modified: 2020-06-12 08:52 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.15
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lsusb (650 bytes, text/plain)
2018-02-11 12:45 UTC, Peter Weber
Details
lspci (1.85 KB, text/plain)
2018-02-11 12:45 UTC, Peter Weber
Details
lscpu (1.12 KB, text/plain)
2018-02-11 12:45 UTC, Peter Weber
Details
dmesg (78.45 KB, text/plain)
2018-02-11 12:46 UTC, Peter Weber
Details
/proc/interrupts before a suspend, which is followed by immediate resume (3.20 KB, text/plain)
2018-02-11 12:46 UTC, Peter Weber
Details
/proc/interrupts after immediate resume (3.20 KB, text/plain)
2018-02-11 12:47 UTC, Peter Weber
Details

Description Peter Weber 2018-02-11 12:45:20 UTC
Created attachment 274103 [details]
lsusb

Hello!

My ThinkPad X220 often immediately resumes from suspend, due to issues with bluetooth. My ThinkPad uses a newer bluetooth-chip from a follow up gen (X230, X240...) which features Bluetooth "4.0 LE", see attached lsusb.

After many suspend and resume cycles, the immediate suspend occours usually if a bluetooth is on and a keyboard or mouse is paired, but not connected.
The suspend works fine and is not followed by an immediate resume, if bluetooth is off. It also works fine if bluetooth is ON, a keyboard or mouse is paired and connected.

Maybe something always tries to establish a connection, if not present and causes the resume from suspend?

Thanks

PS: I can delay a suspend while moving around a paired and connected mouse, which subsequently also leeds to a immediate resume. But I doesn't consider this as a big issue.
Comment 1 Peter Weber 2018-02-11 12:45:40 UTC
Created attachment 274105 [details]
lspci
Comment 2 Peter Weber 2018-02-11 12:45:54 UTC
Created attachment 274107 [details]
lscpu
Comment 3 Peter Weber 2018-02-11 12:46:13 UTC
Created attachment 274109 [details]
dmesg
Comment 4 Peter Weber 2018-02-11 12:46:47 UTC
Created attachment 274111 [details]
/proc/interrupts before a suspend, which is followed by immediate resume
Comment 5 Peter Weber 2018-02-11 12:47:09 UTC
Created attachment 274113 [details]
/proc/interrupts after immediate resume
Comment 6 Peter Weber 2018-02-11 12:51:08 UTC
The mentioned bluetooth chip:
Bus 003 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]

I tried it with an updated firmware from here[1] and without (uses built-in firmware).

[1] https://github.com/winterheart/broadcom-bt-firmware
Comment 7 Peter Weber 2020-06-12 08:52:35 UTC
Fixed a long time ago by an unknown change.

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