From: Yong Zhang <yong.zhang0@gmail.com>
To: "Nallasellan, Singaravelan" <singaravelan.nallasellan@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Player Thread is not woken after period elapsed
Date: Wed, 14 Sep 2011 16:39:17 +0800 [thread overview]
Message-ID: <20110914083916.GA23710@zhy> (raw)
In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C4317651@bgsmsx502.gar.corp.intel.com>
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
next prev parent reply other threads:[~2011-09-14 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 17:38 Player Thread is not woken after period elapsed Nallasellan, Singaravelan
2011-09-05 17:52 ` Arjan van de Ven
2011-09-05 18:08 ` Nallasellan, Singaravelan
2011-09-05 18:22 ` Arjan van de Ven
2011-09-06 14:19 ` Nallasellan, Singaravelan
2011-09-07 3:06 ` Arjan van de Ven
2011-09-07 12:02 ` Nallasellan, Singaravelan
2011-09-08 2:13 ` Yong Zhang
2011-09-08 7:29 ` Yong Zhang
2011-09-08 9:45 ` Nallasellan, Singaravelan
2011-09-09 6:07 ` Yong Zhang
2011-09-09 12:42 ` Nallasellan, Singaravelan
2011-09-14 8:39 ` Yong Zhang [this message]
2011-09-14 9:18 ` Shan Hai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110914083916.GA23710@zhy \
--to=yong.zhang0@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=singaravelan.nallasellan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox