Intel Bluetooth fails after hours of operation

[stooovie]

Hi, Bluetooth (Intel, device ID 8087:07dc) recently (one or two weeks) started to repeatedly and frequently fail after a year of flawless operation. I have Home Assistant running as a VM in Proxmox. There has been no Proxmox update in the time it started happening, and it had an uptime of two months.

It does work for hours up to roughly a day after a reboot though! When the failure happens, seemingly only a complete reboot of the Proxmox host gets the BT stack fully up again, which is obviously unacceptable.

I'm on kernel 6.5.11-7-pve, PVE 8.1.3.

root@pve:~# dmesg | egrep -i "blue"
[   12.586406] Bluetooth: Core ver 2.22
[   12.586429] NET: Registered PF_BLUETOOTH protocol family
[   12.586431] Bluetooth: HCI device and connection manager initialized
[   12.586435] Bluetooth: HCI socket layer initialized
[   12.586438] Bluetooth: L2CAP socket layer initialized
[   12.586443] Bluetooth: SCO socket layer initialized
[   12.713281] systemd[1]: Reached target bluetooth.target - Bluetooth Support.
[   12.724604] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 2 week 3 2013
[   12.724840] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq failed with error -2
[   12.724843] Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq (-2)
[   12.724875] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2
[   12.724877] Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.7.bseq
[   12.728620] Bluetooth: hci0: Found Intel default device address (00:03:19:9e:8b:00)

Any tips? Thanks!

 

[ffm777]

I have exactly the same problem. Any help would be highly appreciated.

 

[wmehanna]

I know this is an old thread... I was searching for other people hitting this same Intel-integrated-Bluetooth-dies-under-Proxmox problem and found this thread. So i wanted to share what fixed it for me.

This is a really common pattern with Intel integrated BT chips under Proxmox passthrough, not just this thread. The "8087:0a2a not working" thread here i saw the identical "dies after some hours. The only a full host reboot fixes it" behavior for over a year with no real fix either...

The reason a host reboot is what fixes it is that once you pass the chip through, the guest's Bluetooth stack becomes solely responsible for keeping the hardware alive. If it stalls, trips USB autosuspend or lands in a bad firmware state then the guest has no way to reset in a claen way the physical chip, only a full host level USB re-enumeration bn rebooting actually clears it.

I ended up building a small tool that sidesteps this entirely: keep the Bluetooth chip on the host and bridge it to the VM over the network instead of raw USB passthrough.

Here's the open source repo -> https://github.com/lucid-fabrics/proxmox-bluetooth, All is needed is to run 2 commands. I hope this helps you or someone!