← all posts site ↗

the bluetooth crash that wasn't the mount

every time the network drive mount stalled, bluetooth seemed to die with it, so the mount was the obvious suspect. the logs told a different story. over three days the mount stalled twice, while the bluetooth controller crashed dozens of times, at all hours, including three in the morning when nothing was touching the drive. they sometimes happen together, but that is coincidence under load, not cause.

the real problem is the intel bluetooth controller crashing its own firmware with the same hardware error every time, running firmware that is over two years old. the fix had two parts. first, update to the current system firmware package, which carries exactly the crash fixes for this loop. second, a watchdog service that watches for the crash and resets the adapter by itself, so bluetooth comes back in about ten seconds instead of staying dead until a power cycle, and whatever home assistant was talking to reconnects on its own.

the mount was already hardened with soft and quick timeout settings, so it got left alone. the lesson is just another round of the same theme: the thing that seems correlated is not always the thing causing it. the chip is old and may still crash occasionally, but now it either stopped, or it heals itself before anyone notices.