For the uninitiated, git-bisect is a tool for identifying the patch that caused a particular bug. It works on the principle of binary search. Its a really cool thing to use, but it takes a long time to complete (not so much with make -j16 on my new Core 2 Quad!!). I identified that v2.6.24 was good and the current one was bad. (v2.6.24 was released around 15 days ago.) And within those 15 days some 4K odd patches had accumulated and I had to bisect the big pile! But thankfully it was successful and it pointed me to the right commit and hence I was able to fix the problem. Here's the patch - http://lkml.org/lkml/2008/2/8/342.