Description of problem: While booting the system some bluetooth errors occur. How reproducible: Turn bluetooth off and reboot your system. Steps to Reproduce: 1. Turn of bluetooth 2. Reboot your system 3. Check log for errors Actual results: Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19) Bluetooth: hci0 command 0xfc8e tx timeout Bluetooth: hci0 sending frame failed (-19) Bluetooth: hci0 command 0xfc11 tx timeout Bluetooth: hci0 exiting Intel manufacturer mode failed (-110) Expected results: No errors during boot. Workaround: "systemctl enable bluetooth" and all the errors are gone. It's a fresh install of fedora 28 and it should work without running some extra commands. Even eliminates some rfkill errors. Additional info: Bluetooth: hci0: read Intel version: 370810011003110e00 Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
(In reply to Sebastian from comment #0) > Description of problem: While booting the system some bluetooth errors occur. > > > How reproducible: Turn bluetooth off and reboot your system. If bluetoothd isn't running, then those warnings aren't coming from bluetoothd. Then they're coming from the kernel.
(In reply to Bastien Nocera from comment #1) > If bluetoothd isn't running, then those warnings aren't coming from > bluetoothd. Then they're coming from the kernel. Bluetoothd is running. [user@localhost-localdomain ~]$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor p> Active: active (running) since Wed 2018-06-13 17:06:59 CEST; 29min ago Docs: man:bluetoothd(8) Main PID: 894 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 2.2M CGroup: /system.slice/bluetooth.service └─894 /usr/libexec/bluetooth/bluetoothd P.S.: "systemctl enable bluetooth" did only help for some reboots. Errors are back now.
Bluetoothd was always on, but typing "systemctl enable bluetooth" make the errors disappear for a while.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.17.7-200.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
The problem is still persisten with the newer kernel.
Kernel version: 4.17.7-200.fc28.x86_64
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Still the same errors on 4.18.10-200.fc28.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Same on 4.20.4-200.fc29.x86_64.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Seems to be resolved on Fedora 30(5.1.5-300.fc30.x86_64).
Errors are back after some updates. 5.1.19-300.fc30.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
Bluetooth: hci0: unexpected event for opcode 0xfc2f
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
(In reply to Justin M. Forbes from comment #17) > *********** MASS BUG UPDATE ************** > > We apologize for the inconvenience. There are a large number of bugs to go > through and several of them have gone stale. Due to this, we are doing a > mass bug update across all of the Fedora 31 kernel bugs. > > Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > > If you have moved on to Fedora 32, and are still experiencing this issue, > please change the version to Fedora 32. > > If you experience different issues, please open a new bug report for those. Issue is still there: 5.5.9-200.fc31.x86_64
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Someone, please don't close the bug, just because the distribution version has changed. Close the bug only when the bug does NOT appear in the new distribution in the SAME hardware. For me, I get Bluetooth bugs all the time. I want it to get fixed. I'm using Fedora 34. The sad thing is this bug was reported in 2018 and a user like me still has to experience the same issue in 2021. pranav@fedora ~> uname -r 5.13.10-200.fc34.x86_64 pranav@fedora ~> sudo journalctl -k | grep -A 1 -B 1 -i 'bluetooth' | xclip -selection clipboard Aug 20 07:59:43 fedora kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Aug 20 07:59:43 fedora kernel: Bluetooth: Core ver 2.22 Aug 20 07:59:43 fedora kernel: NET: Registered protocol family 31 Aug 20 07:59:43 fedora kernel: Bluetooth: HCI device and connection manager initialized Aug 20 07:59:43 fedora kernel: Bluetooth: HCI socket layer initialized Aug 20 07:59:43 fedora kernel: Bluetooth: L2CAP socket layer initialized Aug 20 07:59:43 fedora kernel: Bluetooth: SCO socket layer initialized Aug 20 07:59:43 fedora kernel: input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input21 -- Aug 20 07:59:43 fedora kernel: at24 6-0050: supply vcc not found, using dummy regulator Aug 20 07:59:43 fedora kernel: Bluetooth: hci0: read Intel version: 3707100100012d0d00 Aug 20 07:59:43 fedora kernel: at24 6-0050: 256 byte spd EEPROM, read-only Aug 20 07:59:43 fedora kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq Aug 20 07:59:43 fedora kernel: iTCO_wdt iTCO_wdt.1.auto: Found a Wildcat Point_LP TCO device (Version=2, TCOBASE=0x1860) -- Aug 20 07:59:43 fedora kernel: audit: type=1130 audit(1629425683.798:109): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-backlight@leds:dell::kbd_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Aug 20 07:59:43 fedora kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f Aug 20 07:59:43 fedora kernel: Bluetooth: hci0: Intel BT fw patch 0x27 completed & activated Aug 20 07:59:43 fedora kernel: intel_rapl_common: Found RAPL domain package -- Aug 20 07:59:45 fedora kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Aug 20 07:59:45 fedora kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Aug 20 07:59:45 fedora kernel: Bluetooth: BNEP filters: protocol multicast Aug 20 07:59:45 fedora kernel: Bluetooth: BNEP socket layer initialized Aug 20 07:59:45 fedora kernel: vmmon: loading out-of-tree module taints kernel. -- Aug 20 07:59:56 fedora kernel: rfkill: input handler disabled Aug 20 07:59:56 fedora kernel: Bluetooth: RFCOMM TTY layer initialized Aug 20 07:59:56 fedora kernel: Bluetooth: RFCOMM socket layer initialized Aug 20 07:59:56 fedora kernel: Bluetooth: RFCOMM ver 1.11 Aug 20 07:59:59 fedora kernel: userif-2: sent link down event. -- Aug 20 15:06:21 fedora kernel: PM: suspend exit Aug 20 15:06:21 fedora kernel: Bluetooth: hci0: read Intel version: 3707100100012d0d00 Aug 20 15:06:21 fedora kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq Aug 20 15:06:22 fedora kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f Aug 20 15:06:22 fedora kernel: Bluetooth: hci0: Intel BT fw patch 0x27 completed & activated Aug 20 15:06:25 fedora kernel: wlp3s0: authenticate with e8:d0:b9:ac:10:d9