Without more information, I cannot provide any further analysis or even indications where to look to recreate or further isolate possible causes.
I would like to point out that there was a kernel patch this week that was both
committed to 5.4-stable and
published as a patch to 5.4-release, to eliminate a problem with the pflow(4) driver.