Comment 27 for bug 1768627

@Mauro,

Okay, perfect thanks. So from this debug log we can tell for sure that this isn't caused by thunderbolt power, but rather the value read from the kernel immediately is invalid.
This tells me that this is probably a case of fwupd racing with the kernel based off the uevent that came through.

I've filed an issue upstream that we can discuss this more with relevant developers to see if we can come up with a better solution.
https://github.com/hughsie/fwupd/issues/608