Comment # 5 on bug 107781 from 
Any chance you can try if the problem also occurs with an upstream 4.17 or 4.18
kernel?

You are receiving this mail because: