Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Sender: Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Date:   Sat, 13 Feb 2021 08:33:58 +0100
From:   Salvatore Bonaccorso <carnil@debian.org>
To:     =?utf-8?Q?Micha=C5=82?= Zegan <webczat_200@poczta.onet.pl>
Cc:     linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth not working in 5.10 kernel?
Message-ID: <YCeA5hF+5yn4w/EY@eldamar.lan>
References: <ddf00862-515e-a295-dbcc-068592220e94@poczta.onet.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ddf00862-515e-a295-dbcc-068592220e94@poczta.onet.pl>
Precedence: bulk

Hi Michał,

On Thu, Feb 11, 2021 at 11:42:39PM +0100, Michał Zegan wrote:
> Hi,
> I have 5.10.13 kernel on archlinux and bluetooth seems to misbehave.
> Not sure if that is known or fixed?
> Namely, I have some atheros bluetooth using btusb driver or so it seems,
> laptop lenovo ideapat 310.
> I managed to turn it on, then when turning on bluetooth on my phone
> (devices are paired) it triggered connection with the pc, but my sound
> suddenly silenced, then after a minute I got a connection error on phone
> and pc went back to normal.
> Then I tried again, this time my sound started looping on the pc, and
> after some time went back to normal, phone showed errors again.
> I removed the pairing at phone side, disabled bluetooth from gnome and
> tried to reload the driver (btusb).
> However, now bluez does not detect my adapter, bluetoothctl command
> "list" shows nothing. Gnome tries to turn on bluetooth but shows it
> turned off each time.
> In addition, even though list is empty, I see the device in
> /sys/class/bluetooth.
> I have found some reddit thread about a similar issue,
> https://www.reddit.com/r/archlinux/comments/kwpw6j/bluetooth_not_working_anymore/

See both reports at

https://bugzilla.kernel.org/show_bug.cgi?id=210681
and
https://bugzilla.kernel.org/show_bug.cgi?id=211571

So the fix is now pending in bluetooth-next.

Regards
Salvatore