Please always test bugs like this with a recent kernel. 2.6.35 is pretty much 6 versions (and 18 months) behind and at that point you really have to test with something newer first before asking others to help you and spend their time on your problem.
Unfortunately, I am stuck with that version as the product that I work on is on that version.
and that is everyone elses problem ... how?
if you can't be bothered to try at least a recent kernel, why would anyone else be bothered to help you on their own time?????
I completely agree with you. Sorry for the inconvenience. But I have no choice. Further investigation of this issue shows that the thread is in running state and it is not scheduled. I am not sure how I will go about debugging this issue. Any pointer would help.
--