Comment # 2 on bug 1070020 from
Newest 4.14.2 kernel fixed this problem for me.


You are receiving this mail because: