[Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot

https://bugzilla.kernel.org/show_bug.cgi?id=213829

--- Comment #30 from Marco (rodomar705@protonmail.com) ---

(In reply to Kiran from comment #29)

(In reply to Marco from comment #27)

quoted

(In reply to Guillaume Binet from comment #26)

quoted

Alright, talking with Intel directly, this patch seems to fix it for

5.15.2:

quoted

https://patchwork.kernel.org/project/bluetooth/patch/20211013080511.23945-1-

quoted

quoted

kiran.k@intel.com/

I have a bunch of other regressions like GPU hangs with 5.15 but at least

I

quoted

quoted

see the controller showing up consistently warm reboot after warm reboot.

Can anyone else confirm it works?

Nope, running 5.15.2 and now bluetooth disappears after a reboot. This
hasn't fixed the problem for me, it just changed behaviour.

I can confirm that the patch is present, I do see the message added for

that

quoted

patch:
....
[13556.611182] Bluetooth: hci0: No device address configured
[13556.611197] Bluetooth: hci0: Found device firmware:
...

But there is no bluetooth adapter available from both my DE nor from
bluetoothctl info command.

The log "No device address configured" was present even before this patch.
https://patchwork.kernel.org/project/bluetooth/patch/20211013080511.23945-1-
kiran.k@intel.com/

Now its getting printed conditionally based on the mode of the controller.
Are your sure that this patch is present in your test? As of now I can see
this patch merged only in maintainer tree but not in 5.15-rc2

Thanks,
Kiran

I'm sorry, Kiran, you were 100% right, even the stock kernel hasn't yet
included that patch. After compiling 5.15.2 plus the above mentioned patch, I
can definitively confirm that on my system the issue is completely fixed.
Rebooted 5 times, each time the bluetooth was working correctly. Finally this
bug is fixed, I hope it will be merged soon, at least on the 5.15 series.

Thanks a lot for your work,

Marco.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.