From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753266Ab1IESTN (ORCPT ); Mon, 5 Sep 2011 14:19:13 -0400 Received: from casper.infradead.org ([85.118.1.10]:47753 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751990Ab1IESTJ (ORCPT ); Mon, 5 Sep 2011 14:19:09 -0400 Date: Mon, 5 Sep 2011 11:22:25 -0700 From: Arjan van de Ven To: "Nallasellan, Singaravelan" Cc: "alsa-devel@alsa-project.org" , "linux-kernel@vger.kernel.org" Subject: Re: Player Thread is not woken after period elapsed Message-ID: <20110905112225.72b46ac9@infradead.org> In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C420F15C@bgsmsx502.gar.corp.intel.com> References: <3CA6C6D9F70D314CA34352990B57DA1507C420F147@bgsmsx502.gar.corp.intel.com> <20110905105253.2787b91f@infradead.org> <3CA6C6D9F70D314CA34352990B57DA1507C420F15C@bgsmsx502.gar.corp.intel.com> Organization: Intel X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 5 Sep 2011 23:38:49 +0530 "Nallasellan, Singaravelan" 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