From: Guillaume Clement <gclement@baobob.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [snd-usb-audio] frequent "delay: estimated xxx, actual yyy" messages
Date: Wed, 25 Apr 2012 20:06:57 +0200 [thread overview]
Message-ID: <1376468.6QcoDNaDHT@siegfried> (raw)
In-Reply-To: <4F96B1B3.1060606@ladisch.de>
Le mardi 24 avril 2012 15:59:15 vous avez écrit :
> Guillaume Clement wrote:
> > Could the delay not be the cause, but a side effect ?
>
> Yes, that's probable. It might be possible that some interrupt got
> delayed too much, or that packets were completed in wrong order.
I've noticed that using the touchpad triggers the issues, even in console mode
when I don't start X. Some other factors seem to trigger it, like some
graphical operations or hard disk usage (but again, only when the CPU is low
usage).
I forgot to mention that my integrated soundcard does not have this issue. I
deactivated the integrated soundcard in the BIOS and that didn't help.
>
> > Do you have any idea why keeping my CPU busy removes the problem ?
>
> I'd guess that an idle CPU needs a longer time to wake up.
> What CPU and what CPU frequency governor are you using?
On my laptop, I've got an Atom Z520 @ 1.33GHz. I was using the ondemand
governor. I switched to performance, with no effect.
I tried to disable as many modules as possible (even my graphics card, wifi,
touchscreen) with no luck so far.
I tried again on several of my other computers and I could not reproduce the
problem, even on another netbook. It's quite weird becaues I thought I
reproduced it with several hardware back in December, but I guess I was
mistaken, sorry about that.
prev parent reply other threads:[~2012-04-25 18:07 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
2012-04-24 13:59 ` Clemens Ladisch
2012-04-25 18:06 ` Guillaume Clement [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=1376468.6QcoDNaDHT@siegfried \
--to=gclement@baobob.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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).