Bug 211983 - BUG: Unable to toggle bluetooth ON once switched off using rfkill
Summary: BUG: Unable to toggle bluetooth ON once switched off using rfkill
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-27 16:22 UTC by Kunal Bhat
Modified: 2021-07-27 15:19 UTC (History)
7 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kunal Bhat 2021-02-27 16:22:44 UTC 
As the title suggests, the only way to toggle bluetooth on is by restarting the  bluetoothd service. Once Bluetooth has been switched off using rfkill/other frontends, it refuses to turn back on, even though rfkill reports hci0(bluetooth) as unblocked.

It works just fine on 5.10.16.

Steps to reproduce: 
Disable bluetooth with rfkill and try enabling it again.

Hardware: Intel Corp. Wireless-AC 9260 Bluetooth Adapter
Kernel Version: 5.11.1 and 5.11.2

Tried reading journalctl and dmesg outputs to no avail. Let me know if there's any logs that I can acquire.
Comment 1 Kunal Bhat 2021-02-28 06:58:13 UTC 
Changing the problematic component to USB since it seems to affect more than bluetooth. My USB mouse is recognised on connecting, but doesn't seem to function unless I boot up the system with it connected.
Comment 2 juliusvonkohout 2021-04-24 14:00:03 UTC 
Same problem on fedora 34 and ubuntu 21.04 with kernel 5.11.
I am using an intel ax201 card.
Comment 3 juliusvonkohout 2021-04-25 07:44:28 UTC 
There seem to be Fedora downstream bugs https://bugzilla.redhat.com/show_bug.cgi?id=1944482
Comment 4 Kunal Bhat 2021-07-27 15:19:15 UTC 
Was fixed in 5.12 but seems to have reappeared in 5.13
Note You need to log in before you can comment on or make changes to this bug.