On Mon 05 Dec 2022 at 08:42:14 (-0600), d...@sherohman.org wrote: > I've got a headless server which is endlessly spamming its logs multiple > times per second with: > > --- > Dec 5 15:22:33 fubar systemd[2097]: Reached target Bluetooth. > Dec 5 15:22:33 fubar systemd[2093386]: Reached target Bluetooth. > Dec 5 15:22:33 fubar systemd[2093386]: Stopped target Bluetooth. > Dec 5 15:22:33 fubar systemd[2097]: Stopped target Bluetooth. > Dec 5 15:22:33 fubar kernel: [2937739.971268] usb 1-14: new full-speed USB > device number 119 using xhci_hcd > Dec 5 15:22:33 fubar kernel: [2937740.121486] usb 1-14: New USB device > found, idVendor=8087, idProduct=0032, bcdDevice= 0.00 > Dec 5 15:22:33 fubar kernel: [2937740.121493] usb 1-14: New USB device > strings: Mfr=0, Product=0, SerialNumber=0 > Dec 5 15:22:33 fubar kernel: [2937740.124798] Bluetooth: hci0: Reading Intel > version information failed (-22) > Dec 5 15:22:33 fubar kernel: [2937740.124813] Bluetooth: hci0: Intel Read > version failed (-22) > Dec 5 15:22:33 fubar kernel: [2937740.124972] Bluetooth: hci0: Intel reset > sent to retry FW download > Dec 5 15:22:33 fubar kernel: [2937740.125348] usb 1-14: USB disconnect, > device number 119 > Dec 5 15:22:33 fubar systemd[2046734]: Reached target Bluetooth. > Dec 5 15:22:33 fubar systemd[2046734]: Stopped target Bluetooth. > --- > > How do I kill bluetooth dead and make this stop? > > I do not need help making bluetooth load correctly. The machine does > not need or want bluetooth connectivity. If bluetooth were running > successfully, the first and last thing I would do with bluetooth would > be to disable it. > > The question is how to make it stop attempting to load bluetooth in the > first place. > > Based on some web searches, I have already tried: > > - Checking the output of `dpkg --get-selections` for any package names > mentioning "blue", "tooth", or "bt" - there aren't any, so the obvious > solution of `apt-get remove --purge bluetooth` doesn't appear to be an > option > > - `rmmod btusb` - this has no apparent effect, probably because > bluetooth.target loads the mod back in before I even have time to run > `lsmod` and see if it's still there
Then I would blacklist it. Create a blacklist-bluetooth.conf file in /lib/modprobe.d/ and containing blacklist btusb or whichever modules (one per line), before removing it/them. > - `systemctl X bluetooth.target` for X in (stop, disable, mask) - this > has also had no apparent effect; even with the target stopped, > disabled, and masked, the system still keeps reaching it and trying to > read the Intel version information > > - grepping for the text 'bluetooth.target' in all files in /etc/systemd/ > and /usr/lib/systemd/ (so I could find out what 'wants > bluetooth.target') - no matches were found Cheers, David.
