Apparently this is a kernel issue caused by
https://bugzilla.kernel.org/show_bug.cgi?id=61781 . Like mentioned in the
bug report, rolling back to kernel 3.10 solved the issue for me.

Reply via email to