Originally Posted by epsilon72
I've just found that this problem exists with kernels as early as 2.6.32. Although it is not as apparent, the problem is still there.
That's right, I first observed this bug in November of 2010, on a regular 2.6.32-series kernel update on Ubuntu Lucid. Started happening with 2.6.32-26 IIRC. The update included, amongst other things, a respectable amount of kernel scheduler fixes/changes ... Maybe related, I don't know.
This issue has been present ever since, as far as I have observed.
Bug report and changelog of the kernel update: