Comment 10 for bug 1034099

I'd like to perform a kernel bisect to identify what commit caused this regression. It sounds like this regression was introduced in 3.2.0-29.46, so I will bisect between 3.2.0-28.45 and 3.2.0-29.46.

I'm going to first see if I can reproduce this bug. If I can, I can perform the bisect and testing. Is installing the ulatencyd package all that is required, or do I need to do some configuring of ulatencyd?

This bug may be related to commit ffaf6a1e73719e0250fce7b52015187180a77fe9 . In parallel with bisecting, I'm going to build a test kernel with that commit reverted. I'll post a link to that test kernel shortly.