From: Chris <cpollock@embarqmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Which project to choose?
Date: Wed, 21 Jul 2010 17:57:55 -0500 [thread overview]
Message-ID: <1279753075.30218.14.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilnHVzNmIOMxkCVjXGwsXdKyC_vI54kpwAFtIh8@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2710 bytes --]
On Wed, 2010-07-21 at 16:17 +0800, Raymond Yau wrote:
> 2010/7/21 Chris <cpollock@embarqmail.com>
>
> > Before I try the above Raymond, what would cause the below when the
> > system is sitting here basically idle? I'm not even home to do anything
> > when this happened?
>
>
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:43 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: ratelimit.c: 240 events
> > suppressed
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> > Jul 20 11:32:45 localhost pulseaudio[28711]: asyncq.c: q overrun,
> > queuing locally
> >
> >
> I don't think the system is idle , you still have the
> gnome-volume-mixer-applet / kmix connected to PA server using pulse api
>
> pactl stat
>
> pactl list
>
> you have to ask PA developers because I cannot reproduce "asyncq.c: q
> overrun," in the virtualbox
Raymond, outputs of above are here:
http://pastebin.com/db20pXi9
--
Chris
KeyID 0xE372A7DA98E6705C
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-07-21 22:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 23:02 Which project to choose? Chris
2010-07-13 23:26 ` Raymond Yau
2010-07-14 0:01 ` Chris
2010-07-14 1:20 ` Raymond Yau
2010-07-14 1:31 ` Chris
[not found] ` <AANLkTimNSRELBq7i1Ypi9K2tmFu9NKLvQAOOqPwuU13x@mail.gmail.com>
[not found] ` <1279074303.29042.3.camel@localhost.localdomain>
2010-07-14 12:23 ` Raymond Yau
2010-07-14 22:15 ` Chris
2010-07-15 0:08 ` Raymond Yau
2010-07-15 1:38 ` Chris
2010-07-15 12:58 ` Colin Guthrie
2010-07-15 14:07 ` Jaroslav Kysela
2010-07-15 22:54 ` Chris
2010-07-15 23:15 ` Raymond Yau
2010-07-16 0:24 ` Chris
2010-07-16 5:32 ` Jaroslav Kysela
2010-07-16 1:19 ` Chris
2010-07-16 5:40 ` Jaroslav Kysela
2010-07-17 0:22 ` Raymond Yau
2010-07-15 22:02 ` Raymond Yau
2010-07-19 1:44 ` Raymond Yau
2010-07-19 2:56 ` Chris
2010-07-19 6:35 ` Raymond Yau
2010-07-19 7:53 ` Colin Guthrie
2010-07-19 22:52 ` Chris
2010-07-20 1:23 ` Raymond Yau
2010-07-20 2:13 ` Chris
2010-07-20 11:41 ` Raymond Yau
2010-07-20 22:19 ` Chris
2010-07-21 8:17 ` Raymond Yau
2010-07-21 22:57 ` Chris [this message]
2010-07-22 0:33 ` Raymond Yau
2010-07-22 1:07 ` Chris
[not found] ` <AANLkTim7iY_w96CPkVIlyB7Z9NGWUIvX2wKwvgu4wdjn@mail.gmail.com>
[not found] ` <1279766127.7841.11.camel@localhost.localdomain>
[not found] ` <AANLkTim_FkOXlYihEQikJ8Vpo5zXreCdqQnDW3acsrAu@mail.gmail.com>
[not found] ` <1279797682.7841.15.camel@localhost.localdomain>
2010-07-22 11:42 ` Raymond Yau
2010-07-20 22:49 ` Chris
2010-07-24 3:51 ` Raymond Yau
2010-07-25 14:14 ` Colin Guthrie
2010-07-26 5:53 ` Raymond Yau
2010-07-26 8:09 ` Raymond Yau
2010-07-15 13:08 ` Raymond Yau
2010-07-14 22:32 ` Raymond Yau
2010-07-14 22:58 ` Chris
2010-07-14 11:13 ` Raymond Yau
2010-07-14 15:06 ` David Henningsson
2010-07-14 15:25 ` Jaroslav Kysela
2010-07-14 19:45 ` David Henningsson
2010-07-14 22:13 ` Jaroslav Kysela
2010-07-16 0:39 ` Raymond Yau
2010-07-16 1:30 ` Raymond Yau
2010-07-15 0:52 ` Raymond Yau
2010-07-23 11:51 ` Raymond Yau
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=1279753075.30218.14.camel@localhost.localdomain \
--to=cpollock@embarqmail.com \
--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).