Bug 117251 - btusb and/or btintel cannot correctly restore after resume from suspend
Summary: btusb and/or btintel cannot correctly restore after resume from suspend
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-26 20:46 UTC by Yaroslav Isakov
Modified: 2020-01-27 06:42 UTC (History)
1 user (show)

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


Attachments

Description Yaroslav Isakov 2016-04-26 20:46:08 UTC
Hello! I have Lenovo Thinkpad T460s with Wifi/BT chip Intel 8260. There is a problem with bluetooth - device disappears from bluetoothctl list. I could see such error message in the log file:
[ 9077.430266] Bluetooth: hci0: Failed to send firmware data (-38)
If I manually rmmod btusb && modprobe btusb, I could see:
[ 9220.767742] usbcore: deregistering interface driver btusb
[ 9225.687528] usbcore: registered new interface driver btusb
[ 9225.689227] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 9225.694233] Bluetooth: hci0: Device revision is 5
[ 9225.694240] Bluetooth: hci0: Secure boot is enabled
[ 9225.694243] Bluetooth: hci0: OTP lock is enabled
[ 9225.694246] Bluetooth: hci0: API lock is enabled
[ 9225.694249] Bluetooth: hci0: Debug lock is disabled
[ 9225.694254] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 9225.694561] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 9227.605395] Bluetooth: hci0: Waiting for firmware download to complete
[ 9227.606321] Bluetooth: hci0: Firmware loaded in 1883432 usecs
[ 9227.606505] Bluetooth: hci0: Waiting for device to boot
[ 9227.618390] Bluetooth: hci0: Device booted in 11793 usecs
[ 9227.618463] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[ 9227.620415] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 9227.621411] Bluetooth: hci0: Setting Intel event mask failed (-16)
and everything will start working again. I'm using linux-firmware-20160331.
Comment 1 Yaroslav Isakov 2016-04-26 20:52:16 UTC
Maybe it's some race issue between iwlwifi and btusb, because I could also see this error message framed by iwlwifi messages:
[ 9582.557934] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9582.559428] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 9582.567217] Bluetooth: hci0: Failed to send firmware data (-38)
[ 9582.692977] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9582.693497] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9582.694872] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
Comment 2 Yaroslav Isakov 2016-04-26 20:59:26 UTC
Ok, here is a full log for after resume:
[ 9900.440872] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 9900.445860] Bluetooth: hci0: Device revision is 5
[ 9900.445865] Bluetooth: hci0: Secure boot is enabled
[ 9900.445868] Bluetooth: hci0: OTP lock is enabled
[ 9900.445870] Bluetooth: hci0: API lock is enabled
[ 9900.445872] Bluetooth: hci0: Debug lock is disabled
[ 9900.445876] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 9900.445880] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 9900.478350] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4762]
[ 9900.514546] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..]
[ 9900.540594] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9900.541872] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9900.543026] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 9900.550896] Bluetooth: hci0: Failed to send firmware data (-38)
[ 9900.677527] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9900.678075] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 9900.679214] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
It seems that bluetooth breaks on "Bluetooth: hci0: Waiting for firmware download to complete" step
Comment 3 RussianNeuroMancer 2020-01-27 06:42:16 UTC
Is it still reproducible for you with Linux 5.5?

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