The issue posted by Tal in #62 looks to be a different issue.
The original issue is about Warm-reboot "command 0xfc05 tx timeout" /
-110 (ETIMEDOUT), which affects AX200 (8087:0029), AX210 (8087:0032),
AX211 (8087:0033), and likely AX201 (8087:0026) and AC9260 (8087:0025).
Tal's issue is "Hardware error 0x0c" / EBUSY (-16) after suspend/resume. This
is a race condition and use-after-free in `btintel_hw_error()`. There is an
upstream commit 94d8e6fe5d08 ("Bluetooth: btintel: serialize btintel_hw_error()
with hci_req_sync_lock"), which is in 7.0-rc6, that may help.
Tal, apprecaite if you could help testing this mainline kernel and tell us if
that fixes your issue. If it doesn't, please file a new bug.
Back to the original bug report, it is caused by the bluetooth device
being in a transient state. On warm reboot, the kernel re-initialises
the device before it's ready, and the first command (`0xfc05` — Intel
Read Version) times out with ETIMEDOUT (-110). There is no recovery path
once this fails. Only a full PSU power cycle or rmmod/modprobe fixes it.
I will upload a patch that tries to fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051720
Title:
Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
