Comment # 1 on bug 70687 from
This happens with 3.12 kernel, with 3.11 it worked just fine.


You are receiving this mail because: