1. Please describe the problem: After upgrading the kernel, bluetooth is not present in the system. Several commands timeout during the boot process: kernel: Bluetooth: hci0: command 0xfc01 tx timeout or kernel: Bluetooth: hci0: command 0xfc05 tx timeout across several boots, only those two were present in the log. 2. What is the Version-Release number of the kernel: kernel-6.8.2-300.fc40, same on kernel-6.9.0-0.rc1.17.fc41 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Works fine on kernel-6.8.1-300.fc40 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Just boot the system, check kernel log 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Not rawhide, but kernel-6.9.0-0.rc1.17.fc41 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Log attached Reproducible: Always
Created attachment 2023816 [details] kernel log from several boots with new kernel Forgot to add, that's Intel AX200 card on MSI Tomahawk X570 WiFi motherboard
Upstream kernel BZ: https://bugzilla.kernel.org/show_bug.cgi?id=218651
Looks like it can be fixed by a revert: https://lore.kernel.org/all/20240314084412.1127-1-johan%2Blinaro@kernel.org/ is it possible to get a -301 kernel with this revert?
FEDORA-2024-7dd4b3b9a4 (kernel-6.8.3-200.fc39 and kernel-headers-6.8.3-200.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4
Proposing as an FE for Final, this looks fairly bad and a reasonable reason to get 6.8.3 in Final.
I can confirm that it's fixed in 6.8.3-300 kernel for F40
I have similar problems with 6.7.11-200.fc39.x86_64 on Fedora 39, bluetooth is not working: dmesg: [ 615.677809] Bluetooth: hci0: Reading Intel version command failed (-110) [ 615.677831] Bluetooth: hci0: command 0xfc05 tx timeout [ 626.301962] Bluetooth: hci0: Reading Intel version command failed (-110) lspci: 08:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Everything works fine with the previous kernel version: 6.7.10-200.fc39.x86_64 Thank you.
David: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 should fix it on F39 (F39 is being bumped to 6.8.x with this update). There was a 6.7.12-200.fc39 built but I think it won't be shipped.
FEDORA-2024-41295cb23c has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-41295cb23c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-41295cb23c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6b7d840efe has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6b7d840efe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6b7d840efe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-7dd4b3b9a4 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7dd4b3b9a4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Adam Williamson from comment #8) > David: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 should > fix it on F39 (F39 is being bumped to 6.8.x with this update). There was a > 6.7.12-200.fc39 built but I think it won't be shipped. Hi, I have installed the update https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 but unfortunately, I'm still experiencing the same issue. I have added my comment to the thread. Thank you.
(In reply to David Laszlo from comment #12) > (In reply to Adam Williamson from comment #8) > > David: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 should > > fix it on F39 (F39 is being bumped to 6.8.x with this update). There was a > > 6.7.12-200.fc39 built but I think it won't be shipped. > > Hi, I have installed the update > https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4 but > unfortunately, I'm still experiencing the same issue. > I have added my comment to the thread. > > Thank you. After reporting my previous issue with the new kernel (which happened after the first reboot after the update), it seems that the problem resolved itself after power off-and power on my computer. Apologies for any confusion caused. Thank you, this update works for me.
ah, yeah, things like bluetooth can sometimes preserve broken state across a reboot. let us know if it comes back, though!
+3 FE in https://pagure.io/fedora-qa/blocker-review/issue/1558 , marking accepted.
FEDORA-2024-6b7d840efe (kernel-6.8.4-300.fc40 and kernel-headers-6.8.3-300.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-7dd4b3b9a4 (kernel-6.8.4-200.fc39 and kernel-headers-6.8.3-200.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-41295cb23c (kernel-6.8.4-100.fc38 and kernel-headers-6.8.3-100.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.