[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3CA6C6D9F70D314CA34352990B57DA1507C42C3CA5@bgsmsx502.gar.corp.intel.com>
Date: Thu, 8 Sep 2011 15:15:38 +0530
From: "Nallasellan, Singaravelan" <singaravelan.nallasellan@...el.com>
To: Yong Zhang <yong.zhang0@...il.com>
CC: Arjan van de Ven <arjan@...radead.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Player Thread is not woken after period elapsed
> > > 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?
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.
Powered by blists - more mailing lists