I couldn’t reproduce this with Fedora, but as soon as I reinstalled tumbleweed, it’s back, so I suspect this is distro-specific.
I got better logs, hopefully:
What I failed to understand previously, is that when I got this message:
Jan 02 18:20:33 andromeda kernel: BUG: workqueue lockup - pool cpus=14 node=0 flags=0x0 nice=0 stuck for 58s!
I should have checked the logs 58s before that. Now I did that, and things seem to go wrong here (@ 18:19:35, as you’d expect):
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command timed out
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware (-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110)
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabilities (-110)
Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authentication Failed (0x05)
which in turn might be caused by what’s happening a couple of seconds earlier.