Comment 18 for bug 1780806

I'm sorry for the delayed answer, I was three weeks on holidays without my laptop. Now I'm back and willing to test what is needed to help fix the problem.

At least the currently most recent kernels (4.15.0-30 from the mainline and 4.15.0-31 from proposed) still both exhibit the same problem.