Messages in this thread |  | | | Date | Thu, 8 Sep 2011 15:29:48 +0800 | | From | Yong Zhang <> | | Subject | Re: Player Thread is not woken after period elapsed |
| |
On Thu, Sep 08, 2011 at 10:13:27AM +0800, Yong Zhang wrote: > On Wed, Sep 07, 2011 at 05:32:10PM +0530, Nallasellan, Singaravelan wrote: > > > > > > > > > > > > > > > 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. > > Could you confirm if [commit f26f9af Sched: fix skip_clock_update optimization] > residents in your kernel?
And commit da7a735e51f9622eb3e1672594d4a41da01d7e4f http://marc.info/?l=linux-kernel&m=129527509622696&w=2
Thanks, Yong
|  |