Intel AX210 Bluetooth controller doesn't start from warm boot

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

Ron M ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Ron M ([email protected]) ---
I have verified this issue is still present in 5.14.0 (and not present in 5.12.19)

You may reply to this email to add a comment.

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

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

--- Comment #13 from Guillaume Binet ([email protected]) ---
I continued to investigate. The major difference between a cold boot and a warm boot is the driver trying to load a firmware.

For the science, I just disabled this behavior and it looks like the device and driver recover on a warm boot. Consider this a workaround and not a fix but at least it works for me, bluetooth is available on a warm boot.

```
pal ➜  linux-5.14.12  diff -u drivers/bluetooth/btintel.c.old
drivers/bluetooth/btintel.c 
--- drivers/bluetooth/btintel.c.old     2021-10-17 13:56:23.583338189 -0400
+++ drivers/bluetooth/btintel.c 2021-10-17 14:01:16.113344330 -0400
@@ -1034,17 +1034,6 @@
                /* Skip reading firmware file version in bootloader mode */
                if (ver->fw_variant == 0x06)
                        break;
-
-               /* Skip download if firmware has the same version */
-               if (btintel_firmware_version(hdev, ver->fw_build_num,
-                                            ver->fw_build_ww,
ver->fw_build_yy,
-                                            fw, boot_param)) {
-                       bt_dev_info(hdev, "Firmware already loaded");
-                       /* Return -EALREADY to indicate that the firmware has
-                        * already been loaded.
-                        */
-                       return -EALREADY;
-               }
        }

        /* The firmware variant determines if the device is in bootloader
@@ -1074,21 +1063,6 @@
        int err;
        u32 css_header_ver;

-       /* Skip reading firmware file version in bootloader mode */
-       if (ver->img_type != 0x01) {
-               /* Skip download if firmware has the same version */
-               if (btintel_firmware_version(hdev, ver->min_fw_build_nn,
-                                            ver->min_fw_build_cw,
-                                            ver->min_fw_build_yy,
-                                            fw, boot_param)) {
-                       bt_dev_info(hdev, "Firmware already loaded");
-                       /* Return -EALREADY to indicate that firmware has
-                        * already been loaded.
-                        */
-                       return -EALREADY;
-               }
-       }
-
        /* The firmware variant determines if the device is in bootloader
         * mode or is running operational firmware. The value 0x01 identifies
         * the bootloader and the value 0x03 identifies the operational
```

You may reply to this email to add a comment.

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

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

--- Comment #16 from Marco ([email protected]) ---
After updating to 5.14.15, it got even worse, now it will literally drop the connection with my mouse after 10 seconds and it will stop responding to any command until a complete shutdown, all I get in the logs is a command timeout, it will literally stop responding to my host.

[  358.869054] Bluetooth: hci0: command 0x0804 tx timeout
[  361.045200] Bluetooth: hci0: command 0x041f tx timeout
[  363.093133] Bluetooth: hci0: command 0x0406 tx timeout

[ 1436.437038] Bluetooth: hci0: command 0x0c03 tx timeout
[ 1444.437291] Bluetooth: hci0: HCI reset during shutdown failed

This even after a cold start.

Anyone with the same problem here?

You may reply to this email to add a comment.

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

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

--- Comment #17 from Marco ([email protected]) --- (In reply to Marco from comment #16)

This was fixed after a reinstall of linux-firmware, sorry, the problem after a reboot is still there, though.

You may reply to this email to add a comment.

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

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

Tedd An ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #19 from Tedd An ([email protected]) --- This should be fixed with
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/btintel.c?id=35191a0fe986bacf69bd842de81119dca7970f11

I tried it with 5.15 and didn't see the problem.

You may reply to this email to add a comment.

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

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

--- Comment #20 from Guillaume Binet ([email protected]) --- (In reply to Tedd An from comment #19)

Sorry it is not.

Testing with the framework laptop on
testing/linux 5.15.1.arch1-2

Steps to reproduce: 1. go to the bios and save settings, it starts bt correctly. 2. Just reboot with for example the reboot command or come out of hibernation etc... it fails as usual.

You may reply to this email to add a comment.

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

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

--- Comment #24 from Josh Ellithorpe ([email protected]) --- (In reply to Tedd An from comment #23)

I just tried. I installed the latest linux-firmware-git package that pulled latest.

On cold boot I had bluetoothctl list hang after boot. Then after restarting the bluetooth service, it showed the device but still refused to even do a basic scan.

Failed to start discovery: org.bluez.Error.NotReady

Then after doing another quick cold boot (stayed off only a few seconds), no device was listed at all. =\

You may reply to this email to add a comment.

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

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

--- Comment #25 from Marco ([email protected]) --- (In reply to Josh Ellithorpe from comment #24)

Same thing here, just tested with the latest 5.15 that supposedly should contains the aforementioned fix above:

With the current firmware in linux-firmware, the issue is still the same after a reboot. With the latest firmware (just downloaded ibt-0041-0041.ddc and sfi, but if the wireless portion is needed, I can add that too) and that made things even weirder and weirder. After a cold boot, the adapter was working as standard. Rebooted and the device was disabled by default (my machine is configured to auto enable the bluetooth at boot), but after disabling and reenabling the radio from my DE, the bluetooth reconnected to my mouse for the first time since I've got this adapter under Linux. After another reboot, the radio completely disappeared (not even detected from my DE). I don't really know where the problem resides, but I'm happy that someone is trying to see to the bottom of this.

Marco.

You may reply to this email to add a comment.

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

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

--- Comment #27 from Marco ([email protected]) --- (In reply to Guillaume Binet from comment #26)

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 patch:

...

[ 2470.756299] Bluetooth: hci0: Timed out waiting for suspend events
[ 2470.756315] Bluetooth: hci0: Suspend timeout bit: 6
[ 2470.756345] Bluetooth: hci0: Suspend notifier action (3) failed: -110
[13556.607173] Bluetooth: hci0: Firmware timestamp 2021.39 buildtype 1 build
31878
[13556.611182] Bluetooth: hci0: No device address configured
[13556.611197] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[13556.611306] Bluetooth: hci0: Boot Address: 0x100800
[13556.611308] Bluetooth: hci0: Firmware Version: 134-39.21
[13556.611310] Bluetooth: hci0: Firmware already loaded

...

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

You may reply to this email to add a comment.

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

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

Kiran ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #29 from Kiran ([email protected]) ---

(In reply to Marco from comment #27)

The log "No device address configured" was present even before this patch.
https://patchwork.kernel.org/project/bluetooth/patch/[email protected]/

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

You may reply to this email to add a comment.

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

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

--- Comment #30 from Marco ([email protected]) --- (In reply to Kiran from comment #29)

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.

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

Rohan ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #39 from Rohan ([email protected]) ---
I faced a similar issue
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000403) on Debian unstable, but only with v5.15.3. When I built v5.15.4 of the kernel, it went away.

Applying this patch on 5.15.3 didn't resolve this for me, but simply moving to 5.15.4 did.

You may reply to this email to add a comment.

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

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

Alexander Konotop ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #40 from Alexander Konotop ([email protected]) --- I confirm that it's working with 5.15.5-arch1-1

You may reply to this email to add a comment.

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

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

--- Comment #46 from Tobias Predel ([email protected]) --- After having been fixed for 5.15 series, the issue seems to reappear on linux mainline 5.16, at least on rc 7.

Bluetooth only works after cold boot, but not after warm boot.

Can anyone look into this?
Thanks in advance!

[email protected] <[email protected]> schrieb / wrote / a écrit / je pisao / је писао:

You may reply to this email to add a comment.

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

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

--- Comment #48 from Fabian ([email protected]) --- (In reply to Paul Bryan from comment #47)

It's fixed upstream since 5.15.5 or 6

You may reply to this email to add a comment.

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

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

--- Comment #52 from Apostolos B. ([email protected]) ---

Some like that:

Ιαν 05 18:20:53 mainland bluetoothd[25908]: Loading LTKs timed out for hci0 Ιαν 05 18:20:53 mainland kernel: Bluetooth: hci0: command 0x0c52 tx timeout Ιαν 05 18:20:55 mainland kernel: Bluetooth: hci0: command 0x0c24 tx timeout Ιαν 05 18:20:57 mainland kernel: Bluetooth: hci0: command 0x0c1a tx timeout Ιαν 05 18:20:59 mainland kernel: Bluetooth: hci0: command 0x0405 tx timeout Ιαν 05 18:20:59 mainland kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Ιαν 05 18:21:36 mainland kernel: Bluetooth: hci0: command 0x0408 tx timeout Ιαν 05 18:21:36 mainland kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing

I think those are the ones that are logged when i cant use the mouse any more and need to shutdown completely.

Might be usb related since afai understand the bluetooth adapter is connected via USB.

You may reply to this email to add a comment.

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

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

--- Comment #53 from Marco ([email protected]) --- (In reply to Apostolos B. from comment #52)

Same issues as mine, are you on a Ryzen or Intel?

As far as I have previously debugged, I wasn't unable to pinpoint the cause, since it was happening randomly also on a Realtek radio, so it was either the Bluetooth driver or an actual platform issue (but the external USB ports was still working correctly, therefore I had never been able to find the root cause).

Marco.

You may reply to this email to add a comment.

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