From: Arjan van de Ven <arjan@infradead.org>
To: "Nallasellan, Singaravelan" <singaravelan.nallasellan@intel.com>
Cc: "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: Mon, 5 Sep 2011 11:22:25 -0700 [thread overview]
Message-ID: <20110905112225.72b46ac9@infradead.org> (raw)
In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C420F15C@bgsmsx502.gar.corp.intel.com>
On Mon, 5 Sep 2011 23:38:49 +0530
"Nallasellan, Singaravelan" <singaravelan.nallasellan@intel.com> wrote:
please do not top post!
correcting that mistake for you for this time
>> > User thread which invokes the writei function which in turn
>> > invokes a kernel function which waits for the free buffer to write
>> > the audio data. This kernel function adds this thread to a
>> > wake(sleep) queue and calls a schedule_timeout
>> > (msecs_to_jiffies(10000)).
>
>> actually it doesn't... you must be on some really really old kernel
>> or something.
>>
> Sorry, I have not provided the kernel version. Kernel version is
> 2.6.35.
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.
>> > Will you provide some hint on how to go about identifying the root
>> > cause?
>> https://lkml.org/lkml/2011/9/5/201
> However, wait_for_avail() does not have the code similar to
> the one provided in the patch below.
the patch is against a recent kernel; no surprise that the code has
changed in the last 18 months....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2011-09-05 18:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 17:38 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 [this message]
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
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=20110905112225.72b46ac9@infradead.org \
--to=arjan@infradead.org \
--cc=alsa-devel@alsa-project.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
Powered by JetHome