Comment 103 for bug 1518457

I've fixed this in Arch Linux by moving to the 4.6.1-2-ARCH kernel, when previously on the 4.5.? kernel. This problem also doesn't occur in either the 4.0.7-2 or the 3.16-2 kernels for me at least.

I hear this is happening mostly on the 4.4.0-* kernel, which doesn't seem to be an option in the Arch Linux archive(https://archive.archlinux.org/packages/l/linux/), in fact none of the *.*.0-* kernels are, if you can report a kernel that's in that list I can test it. I have a feeling simply reinstalling any kernel would have fixed it, and I had some sort of configuration problem before.