Hi, we can confirm that using kernel 4.19.28+2 (4.19.0-4) workaround the 
problem.
Kind regards!

Guido

Reply via email to