OK, so lets get the facts straight:
- 2.6.34 does _not_ have the CPU eater problem - 2.6.35-rc1 has the CPU eater problem
Is this correct?
If both of the above are correct, you could try going for
git checkout 1eb2cbb6d5efe129cd006691267ce513c0aa59da
And see if it's good or not. It's the commit that fixes the udev problem. Now if 1eb2cbb6d5efe129cd006691267ce513c0aa59da does _not_ have the CPU eater problem and 2.6.35-rc1 does have it, then just go for:
git bisect reset git bisect start git bisect good 1eb2cbb6d5efe129cd006691267ce513c0aa59da git bisect bad v2.6.35-rc1