From: Guillaume Clement <gclement@baobob.org>
To: alsa-devel@alsa-project.org
Subject: Re: [snd-usb-audio] frequent "delay: estimated xxx, actual yyy" messages
Date: Mon, 23 Apr 2012 21:40:37 +0200 [thread overview]
Message-ID: <1383683.z6YHnxXImd@siegfried> (raw)
In-Reply-To: <4F9594AF.4090902@linux.intel.com>
On 4/23/2012 12:43:11 Pierre-Louis Bossart wrote :
> I'm the one who introduced this warning when I added support for a
> better delay estimate based on the frame counter instead of bytes
> submitted (back in September 2011). When writing new data the estimate
> using the frame counter and the byte count should be identical, but this
> message shows something goes wrong.
> Somehow I don't understand how a more precise delay would cause such
> errors. The delay is only important for pulseaudio, it shouldn't affect
> plain vanilla alsa.
Could the delay not be the cause, but a side effect ? Unfortunately I don't
know anything about the internals here.
What I do know is that there is a lapdesk of another series by the same
vendor, that has exactly the same behaviour. I do know those two lapdesks work
fine under other OSes.
The problem can also be reproduced under various Linux distributions.
Do you have any idea why keeping my CPU busy removes the problem ? That could
be a hint as to where the real problem lies.
> You could try and reverse the patch to see if this
> improves anything? If not, you have another problem in your setup...
By reversing the patch, I made the problem worse.
Is there a way to get more debugging information ? I already tried to get some
output with xrun_debug as pointed in the wiki, but things don't look weird to
me (I only get logs about hwptr_update and period_update)
next prev parent reply other threads:[~2012-04-23 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 10:22 [snd-usb-audio] frequent "delay: estimated xxx, actual yyy" messages Guillaume Clement
2012-04-23 17:43 ` Pierre-Louis Bossart
2012-04-23 19:40 ` Guillaume Clement [this message]
2012-04-24 13:59 ` Clemens Ladisch
2012-04-25 18:06 ` Guillaume Clement
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=1383683.z6YHnxXImd@siegfried \
--to=gclement@baobob.org \
--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;
as well as URLs for NNTP newsgroup(s).