Bug 210275 - Bluetooth stopped working on kernel 5.9
Summary: Bluetooth stopped working on kernel 5.9
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 high
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-20 07:06 UTC by m11.1l1.f64
Modified: 2020-12-09 20:25 UTC (History)
2 users (show)

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


Attachments

Description m11.1l1.f64 2020-11-20 07:06:18 UTC
Bluetooth stopped working on kernel 5.9
It worked well on kernel 5.8

Output of bluetoothctl:
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]#

On the kernel 5.7:
[bluetooth]# show
Controller 70:66:55:BB:04:B6 (public)
        Name: MTN-Lap
        Alias: MTN-Lap
        Class: 0x00000000
        Powered: no
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0537
        Discovering: no
        Roles: central
        Roles: peripheral
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x05 (5)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedSecondaryChannels: Coded

The current kernel:
5.9.8-2-MANJARO

Version of bluetoothctl:
bluetoothctl: 5.55

output of "lsmod | grep bluetooth":
bluetooth             737280  12 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 28672  9 hp_wmi,bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4


System info:
Kernel: 5.9.8-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.20.3 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Comment 1 Jim MacKenzie 2020-11-21 19:05:48 UTC
My Asus Tufbook A17 (8-core Ryzen 7 CPU) running 64-bit Manjaro has precisely the same problem.  Same kernel; same lsmod | grep bluetooth output.  5.8.x works fine.
Comment 2 Francesco Chirico 2020-11-23 20:12:22 UTC
Same problem here after recent updates.
My configuration:

uname -a
Linux Giove 5.9.9-200.fc33.x86_64 #1 SMP Thu Nov 19 21:25:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

lsmod | grep bluetooth
bluetooth             684032  12 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 28672  7 bluetooth,cfg80211

bluetoothctl --version
bluetoothctl: 5.55

sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

sudo hciconfig hci0 up
Can't init device hci0: Protocol not supported (93)

dmesg | grep Bluetooth
[    2.477351] usb 1-1.4: Product: Bluetooth Radio
[    4.851973] Bluetooth: Core ver 2.22
[    4.851993] Bluetooth: HCI device and connection manager initialized
[    4.851995] Bluetooth: HCI socket layer initialized
[    4.851997] Bluetooth: L2CAP socket layer initialized
[    4.852004] Bluetooth: SCO socket layer initialized
[    4.903968] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[    4.904962] Bluetooth: hci0: RTL: rom_version status=0 version=1
[    4.904964] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin
[    4.906676] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_config.bin
[    4.907054] Bluetooth: hci0: RTL: cfg_sz 6, total sz 20522
[    5.033234] Bluetooth: hci0: RTL: fw version 0x0999646b
[   13.214469] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.214471] Bluetooth: BNEP filters: protocol multicast
[   13.214474] Bluetooth: BNEP socket layer initialized
[ 2558.708298] Bluetooth: hci0: command 0x1001 tx timeout
[ 2566.964134] Bluetooth: hci0: RTL: HCI_OP_READ_LOCAL_VERSION failed (-110)
[ 2581.056198] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=0999 lmp_ver=0a lmp_subver=646b
[ 2581.056202] Bluetooth: hci0: RTL: unknown IC info, lmp subver 646b, hci rev 0999, hci ver 000a
[ 2581.056203] Bluetooth: hci0: RTL: assuming no firmware upload needed
Comment 3 Artem S. Tashkinov 2020-11-25 14:14:40 UTC
Please use bisect to find the bad commit.
Comment 4 m11.1l1.f64 2020-11-26 19:02:57 UTC
(In reply to Artem S. Tashkinov from comment #3)
> Please use bisect to find the bad commit.

Could you please explain how I should do that?
Comment 5 m11.1l1.f64 2020-11-28 19:32:12 UTC
Today’s update for the kernel fixed the issue!!
Comment 6 Francesco Chirico 2020-12-09 19:44:33 UTC
(In reply to m11.1l1.f64 from comment #5)
> Today’s update for the kernel fixed the issue!!

Could you please tell what kernel version / package solved the problem?
In my case (Fedora 33) even latest kernel update (5.9.12-200.fc33.x86_64) didn't solve the problem.
Comment 7 Francesco Chirico 2020-12-09 20:25:19 UTC
(In reply to Francesco Chirico from comment #6)
> (In reply to m11.1l1.f64 from comment #5)
> > Today’s update for the kernel fixed the issue!!
> 
> Could you please tell what kernel version / package solved the problem?
> In my case (Fedora 33) even latest kernel update (5.9.12-200.fc33.x86_64)
> didn't solve the problem.

Finally I figured out where the problem was.
In my case I needed a file /etc/modprobe.d/btusb.conf with the following content:

options btusb reset=0

This solved the problem for me.
I wonder why this file became suddenly so important (before I never needed it with the same dongle).

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