Bug 2027071
| Summary: | Rebooting kernel 5.15.4 fails to initialize certain Intel bluetooth devices | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stan King <stanley.king> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 34 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, bugzilla_acct_1959, didierg-divers, erik, gre0, hdegoede, jarodwilson, jeremy, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-5.15.15-100.fc34 kernel-5.15.15-200.fc35 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-01-20 08:33:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Stan King
2021-11-28 00:23:57 UTC
I have the exact same problem, with the same dmesg errors. This bug has also been reported to OpenSuse https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 and to the kernel bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=215167 where it was confirmed to be a regression in kernel 5.15 I also have the exact same problem with same dmesg messages booting on any 5.15 kernel. I have to power off/on my computer to retrieve my BT mouse. I did not have any problem booting on any pre 5.15 kernel. By the way, when dual-booting is an option, booting to the Redmond operating system and back to Linux also usually clears this condition. I too have the same symptoms as Stan King. Like him, I have the hardware: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Using any kernel 5.15, I too get, on booting, the errors: Bluetooth: hci0: Reading Intel version command failed (-110) Bluetooth: hci0: command 0xfc05 tx timeout Bluetooth does then not work at all. The latest tested kernel is 5.15.10, but 5.15.11 (currently the latest) shows no fix in the changelog. There seems to be a recognition from Takashi Iwai, who seems to be a kernel maintainer, in the links given above: https://bugzilla.redhat.com/show_bug.cgi?id=2027071#c1 that a fix already identified is needed for this 8087:0a2a card, but it seems to have fallen through the cracks. Meanwhile, I'm using kernel 5.14.18, as the 5.14 kernels don't have this problem. The fix has not landed in any upstream trees yet (even next). When it does, I will bring it into fedora stable kernels. (In reply to Justin M. Forbes from comment #5) > The fix has not landed in any upstream trees yet (even next). When it does, > I will bring it into fedora stable kernels. "The fix for this issue is in bluetooth-next and will be merged to mainline soon." "https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b" Source: https://lore.kernel.org/lkml/246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info/T/#m77ab9e84eec72d1b3e16d6862ffb1a2670277d94 FEDORA-2022-b7ef5c55da has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b7ef5c55da FEDORA-2022-a23dd56848 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 Installed on Fedora 35 and after Reboot Bluetooth is working fine with 'Intel(R) Dual Band Wireless AC 3165' $ lsusb Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface FEDORA-2022-b7ef5c55da has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b7ef5c55da` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b7ef5c55da See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-a23dd56848 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a23dd56848` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a23dd56848 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. The testing version of the kernel in Comment 11 seems to work for me on the affected hardware. It still seems to skip the firmware reload in case of a "warm" reboot, as distinct from a power cycle. One could reasonably wonder how wise that is. Here is the message that makes me believe that this is the case: Bluetooth: hci0: Intel device is already patched. patch num: 32 Whereas after a power cycle, this message is issued instead: Bluetooth: hci0: Intel BT fw patch 0x32 completed & activated FEDORA-2022-b7ef5c55da has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-a23dd56848 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |