Comment 333 for bug 204996

As I don't have a good way of triggering the bug, I'd like to request that anyone who can do so attempt to find the regression via git-bisect. It's somewhat time-consuming, but it will definitely let us nail down the bug and submit it upstream (as it's appeared in vanilla kernels as well as Ubuntu-specific ones). It would finally make it possible for us to isolate and fix this thing after all these months.

There are good instructions for bisecting the kernel over in bug 273266; I'm willing to help out however I can. If anyone has any specific suggestions for making the bug easily reproducible on my own laptop, I'll try to help out with it as well, though I don't remember the specific revision at which this last didn't happen.