From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Eikum Subject: Re: Infinite loop in snd_pcm_hw_htimestamp() for capture PCMs? Date: Fri, 21 Sep 2012 11:15:59 -0500 Message-ID: <20120921161559.GI4615@foghorn.codeweavers.com> References: <20120921155343.GH4615@foghorn.codeweavers.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.codeweavers.com (mail.codeweavers.com [216.251.189.131]) by alsa0.perex.cz (Postfix) with ESMTP id 08DD6265DB1 for ; Fri, 21 Sep 2012 18:16:01 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: Andrew Eikum , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Fri, Sep 21, 2012 at 06:02:07PM +0200, Takashi Iwai wrote: > At Fri, 21 Sep 2012 10:53:43 -0500, > Andrew Eikum wrote: > > I've found some unexpected behavior in alsa-lib. The attached program > > uses 100% CPU in an infinite loop, when I'd expect it to return either > > an error or a valid htimestamp. I believe the loop occurs in > > . Am I not supposed to call > > htimestamp() on this type of PCM? Is the PCM still in an invalid state > > when htimestamp() is called? > > Indeed, it's a bug in dmix/dsnoop/dshare plugins. > Fixed now in git tree. > Thanks for the fix. Andrew