So, we tried to reproduce it on a different machine at IBM. The problem doesn't show itself there.
I asked the debian admin team to reboot zelenka into 5.10.0-20 kernel to verify, - there was no answer so far. So I'm leaving this as it is now. If the next kernel update will not fix the issue, I'll take another look at it. /mjt
