Yes.. I'm a little confused. For example the previously mentioned thread (id=215167) is still very much ongoing, with some people reporting that certain kernel versions fix this and others reporting it showing up in regressions as late as 6.2.
They referenced a message https://lore.kernel.org/all/[email protected]/ refers to commit 95655456e7cee858a23793f67025765b4c4c227b upstream, which was merged into 5.16 mainline last year. https://lkml.org/lkml/2022/1/14/195 -- I will post back in the bugzilla thread later that this seems to be unrelated. I believe on the Ubuntu side patching from 5.11 to 5.15 caused this problem for me. And it would appear that 5.19 has it as well. But needless to say in "stable LTS" (22.04.2/5.15) this is still happening, breaking bluetooth for Ubuntu users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960016 Title: | Kernel 5.15 Regression | ' Bluetooth: hci0: command tx timeout ' Status in linux package in Ubuntu: Confirmed Bug description: With the current daily-build of 'jammy 22.04' it is not possible to enable Bluetooth with (some) Intel Bluetooth devices after reboot/warm boot. With a Cold boot it is working. My hardware: $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface This is because of a regression in Kernel 5.15 and was present in Fedora and other Distributions as well. https://bugzilla.redhat.com/show_bug.cgi?id=2027071 https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 For example on Fedora35 my Bluetooth did not initialize correctly after warm boot between versions 5.14.18 > 5.15.14. After a cold boot it worked. (Turned off the desktop PC and disconnected it from power for a few seconds.) Kernel 5.15.15 changed that and since then everything went fine again. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 The fix is mentioned there… https://lore.kernel.org/lkml/[email protected]/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 Direct-Link to commit mentioned in the above discussion… https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-20.04 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 12:26:46 2022 InstallationDate: Installed on 2022-02-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220201) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=91d2d15b-9614-4498-bb5c-d3376034009f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F51d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51d:bd12/13/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
