Comment 8 for bug 940771

I can go back to 3.2.0-3.9 from early December and still create the problem though, and I'm certain I was not seeing it back then. So it's not as clear-cut as you make it; there's likely an interaction between the kernel and userspace that's to blame, but who is at fault isn't entirely clear at this point.

That's assuming you and I are seeing the same issue, which I still suspect is the case, but I'm not 100% convinced at this point.