Now it's a different issue.
The original issue, which is the system gets woken up early by btusb, seems to be solved. I don't see "PM: Device 0000:00:14.0 failed to suspend async: error -16" in your new message.
So does this issue happen when Bluetooth is completely disabled?
Now it's a different issue.
The original issue, which is the system gets woken up early by btusb, seems to be solved.
I don't see "PM: Device 0000:00:14.0 failed to suspend async: error -16" in your new message.
So does this issue happen when Bluetooth is completely disabled?