Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76341 - After upgrade to 6.0.5 bluetooth stopped working
Attached to Project:
Arch Linux
Opened by gudvinr (gudvinr) - Saturday, 29 October 2022, 14:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 01 December 2022, 19:44 GMT
Opened by gudvinr (gudvinr) - Saturday, 29 October 2022, 14:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 01 December 2022, 19:44 GMT
|
DetailsYesterday bluetooth was working but I updated kernel that day (from 6.0.2 to 6.0.5) and now after boot with new kernel I am getting error in dmesg:
Oct 29 17:01:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Oct 29 17:01:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) And before that (previous boot with same kernel): Oct 29 16:33:19 kernel: Bluetooth: hci0: Reading Intel version command failed (-16) I have PCIe WiFi/BT card (Intel 8265 / 8275). WiFi works fine. linux-firmware package has version 20220913 and it was installed before too. By the look of it, I think breaking changes were introduced in 6.0.3 because both 6.0.4 and 6.0.5 do not have changes related to bluetooth but 6.0.3 does: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v6.0.3&id2=v6.0.2&dt=2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v6.0.5&id2=v6.0.3&dt=2 |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 01 December 2022, 19:44 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Thursday, 01 December 2022, 19:44 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
The standard set of recommendations for kernel regressions:
- if there is a new kernel in the "testing" repo, try it to see if resolved
- try a precompiled mainline kernel. See the pinned comment here [1]
- report it upstream, either to the kernel bugzilla or to the relevant mailing list (in this case "linux-bluetooth")
- follow the wiki instructions for kernel troubleshooting [2]
- if you're prepared to get "down and dirty", you can perform a git bisection [3] to find the offending commit which can then be reported upstream
- visit the proper Arch support channels (forum/IRC/mailing lists/reddit/etc). You can often find incredibly helpful folks there who will, if you're lucky, even offer to perform a git bisection for you (Hi @loqs! :)
- stay on the last working kernel and hope that a) it gets fixed in a future update or b) someone else comes along and puts in the required effort
Please let us know what you find out.
[1] https://aur.archlinux.org/packages/linux-mainline
[2] https://wiki.archlinux.org/title/Kernel#Troubleshooting
[3] https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
This issue seem to be happening since 5.15 kernel which was released last year.
For now I resort to using 6.0.2 and will upgrade to 6.0.6 from testing when I have time for that. However, I do not see any bluetooth related changes there:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v6.0.6&id2=v6.0.5&dt=2
I didn't report to kernel bugzilla because it says "If you did not compile your own kernel from scratch, you are probably in the wrong place".
I'll try mainline kernel next I guess.
There was a bunch of other updates, including bluez and linux-firmware.