Comment 3 for bug 1517465

I was having a problem rather similar to this (although on different hardware). I found that installing a 4.3.xx version kernel from the mainline builds described above fixed the problem.

(Miraculously, I don't think it broke anything else either!)