From: Daniel Mack <daniel@caiaq.de>
To: alsa-devel@alsa-project.org
Subject: Re: device underruns
Date: Sat, 25 Apr 2009 14:23:38 +0200 [thread overview]
Message-ID: <20090425122338.GE23274@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090331144603.GJ16811@buzzloop.caiaq.de>
The posting below didn't get any response yet, but the problem persists.
Any hints, anyone?
Thanks,
Daniel
On Tue, Mar 31, 2009 at 04:46:03PM +0200, Daniel Mack wrote:
> I'm currently stress-testing my snd-usb-caiaq driver under several
> environments and happen to see a number of such messages echoed once in
> a while at the start of aplay (1.0.16):
>
> underrun!!! (at least 1558380812.470 ms long)
> underrun!!! (at least 1558380818.673 ms long)
> underrun!!! (at least 1558380812.465 ms long)
>
> Also, pulseaudio (0.9.14) keeps complaining with the following message
> all over the place:
>
> E: module-alsa-sink.c: ALSA woke us up to write new data to the device,
> but there was actually nothing to write! Most likely this is an ALSA
> driver bug. Please report this issue to the PulseAudio developers.
>
> What puzzles me a bit is that I don't really know where and how the
> driver could confuse the core so badly. All it reports is a valid
> pointer to the current head in each substream. Is there anything else it
> could provide for tighter syncing? Any hint how to debug this? Or maybe
> it's not a bug in this specific driver but in the core somewhere?
>
> Thanks,
> Daniel
next prev parent reply other threads:[~2009-04-25 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 14:46 device underruns Daniel Mack
2009-04-25 12:23 ` Daniel Mack [this message]
2009-04-26 11:18 ` Takashi Iwai
2009-04-27 10:05 ` Daniel Mack
2009-04-27 10:12 ` Takashi Iwai
2009-04-27 10:18 ` Daniel Mack
2009-04-27 10:36 ` Takashi Iwai
2009-04-27 14:28 ` Daniel Mack
2009-04-27 14:34 ` Takashi Iwai
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=20090425122338.GE23274@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
/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