From: Andrew Eikum <aeikum@codeweavers.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Eikum <aeikum@codeweavers.com>, alsa-devel@alsa-project.org
Subject: Re: Infinite loop in snd_pcm_hw_htimestamp() for capture PCMs?
Date: Fri, 21 Sep 2012 11:15:59 -0500 [thread overview]
Message-ID: <20120921161559.GI4615@foghorn.codeweavers.com> (raw)
In-Reply-To: <s5ha9wjpdog.wl%tiwai@suse.de>
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
> > <src/pcm/pcm_hw.c:snd_pcm_hw_htimestamp()>. 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
prev parent reply other threads:[~2012-09-21 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 15:53 Infinite loop in snd_pcm_hw_htimestamp() for capture PCMs? Andrew Eikum
2012-09-21 16:02 ` Takashi Iwai
2012-09-21 16:15 ` Andrew Eikum [this message]
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=20120921161559.GI4615@foghorn.codeweavers.com \
--to=aeikum@codeweavers.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).