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: Fri, 9 Sep 2011 14:07:25 +0800 [thread overview]
Message-ID: <20110909060725.GA21124@zhy> (raw)
In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C42C3CA5@bgsmsx502.gar.corp.intel.com>
On Thu, Sep 08, 2011 at 03:15:38PM +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?
And BTW, have you tried CONFIG_DETECT_SOFTLOCKUP = y?
Thanks,
Yong
> > >
> > > Could you confirm if [commit f26f9af Sched: fix skip_clock_update
> > > optimization] residents in your kernel?
> I applied this patch manually. I still see the issue.
> >
> > And commit da7a735e51f9622eb3e1672594d4a41da01d7e4f
> > http://marc.info/?l=linux-kernel&m=129527509622696&w=2
> This is already applied.
> \x13��칻\x1c�&�~�&�\x18��+-��ݶ\x17��w��˛���m�b��dz�ޖ)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥>W����i�axP\x10j�m����\f-�\x1a+��d�_
--
Only stand for myself
next prev parent reply other threads:[~2011-09-09 6:07 UTC|newest]
Thread overview: 19+ 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:08 ` Nallasellan, Singaravelan
2011-09-05 18:22 ` Arjan van de Ven
2011-09-06 14:19 ` Nallasellan, Singaravelan
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-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-08 9:45 ` Nallasellan, Singaravelan
2011-09-09 6:07 ` Yong Zhang [this message]
2011-09-09 12:42 ` Nallasellan, Singaravelan
2011-09-09 12:42 ` Nallasellan, Singaravelan
2011-09-14 8:39 ` Yong Zhang
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=20110909060725.GA21124@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.