Comment 27 for bug 89290

It sort of sounds like this issue is has something to do with a mismatch between the versions of the binary driver and the kernel, which may be due to installation order. This may be why installing a new version or performing an upgrade or switching to a different kind of kernel seems to make the issue disappear, only to reappear later. But this is just a gut guess.

It would be worthwhile if people experiencing this problem could track the order of kernel and binary drivers they install, and the versions used.