Although, as it apparently started to happen after a kernel update (5.1.7->5.1.10), it's probably rather a kernel driver problem...