Comment 17 for bug 253089

I forgot to mention...
Interestingly, I first noticed this problem after running a recently compiled 2.6.26 kernel. Thinking it was a badly configured kernel (I did go a bit crazy cutting back the options) I reverted back to my previously stable kernel build, version 2.6.25.9, and the problems continued!
This makes me think, is it possible that this problem could have been inflamed by some recently updated package?