From: Takashi Iwai Subject: Re: Infinite loop in snd_pcm_hw_htimestamp() for capture PCMs? Date: Fri, 21 Sep 2012 18:02:07 +0200 Message-ID: References: <20120921155343.GH4615@foghorn.codeweavers.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id C024D265D7C for ; Fri, 21 Sep 2012 18:02:07 +0200 (CEST) In-Reply-To: <20120921155343.GH4615@foghorn.codeweavers.com> 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: Andrew Eikum Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Fri, 21 Sep 2012 10:53:43 -0500, Andrew Eikum wrote: > > Hi folks, > > 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, Takashi