Bluetooth firmware failed to load on boot, but reloading the module later works

Support
1

So I’ve been wondering why my Bluetooth is not turned on upon login and I would need to:

$ sudo modprobe -vr btusb && sleep 1 && sudo modprobe -v btusb

Inspecting dmesg output, I get this difference:

image
image1959×760 223 KB

Apparently the firmware failed to load on boot, but reloading the module later makes it works.

Any idea what could be the problem? Drive not ready when the module gets probed?

EDIT:
I was to blame, I put btusb into MODULES variable of mkinitcpio.conf. This makes it loaded during the boot process, before the filesystem is ready.