Ok, same here.
Hmmm, since you know a good and bad point, yes a bisect
might be the best way to proceed here.
It might be quicker if you first test 2.6.32 and 2.6.33
and then use the results of that to guide your bisect.
Anyways, if you narrow it down to a commit I should be
able to fix this quickly.
Thanks!
--