14 Sep
2011
14 Sep
'11
10:39 a.m.
On Fri, Sep 09, 2011 at 06:12:03PM +0530, Nallasellan, Singaravelan wrote:
Further investigation of this issue shows that the thread is in running state
Hmm, how do you detect it?
and it is not scheduled. I am not sure how I will go about debugging this
issue.
Any pointer would help.
Could 'cat /proc/sched_debug' give some useful info?
Tried. It did not help.
And BTW, have you tried CONFIG_DETECT_SOFTLOCKUP = y?
It is already set.
That sound at least kwatchdogd could be scheduled suscessfully.
And if CONFIG_DETECT_HUNG_TASK could not bite your "Player Thread", I have no idea what's going on.
Maybe you could try the latest kernel?
Thanks, Yong