Comment 51 for bug 1748565

Ok, you didn't actually read my log output and assume things. The log message disappears completely WHEN my Bluetooth starts working. The actual opposite of your argument. I.e., the message only appears when my machine is "unhealthy". The message does not occur concurrently at all.

Regardless, I can redo my test say 3 times before/after suspend/reboot/logout and if the same pattern occurs it is not a coincident for sure. The message will then be related to the issues (already) reported in several other bug reports.

The coder behind this message is arguing, from what i can surmise, that this is an error that is not handled, not that it is a superfluous debug statement as seen in statements above: https://www.spinics.net/lists/linux-bluetooth/msg75270.html