From: Chris <cpollock@embarqmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Which project to choose?
Date: Thu, 15 Jul 2010 19:24:11 -0500 [thread overview]
Message-ID: <1279239851.12171.1.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilDzdT6X3N2vIBBe-4Br1OJmoefTTutP542DxtJ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2287 bytes --]
On Fri, 2010-07-16 at 07:15 +0800, Raymond Yau wrote:
> 2010/7/16 Chris <cpollock@embarqmail.com>
>
> > On Thu, 2010-07-15 at 16:07 +0200, Jaroslav Kysela wrote:
> > > On Thu, 15 Jul 2010, Colin Guthrie wrote:
> > >
> > > > 'Twas brillig, and Chris at 15/07/10 02:38 did gyre and gimble:
> > > >> On Thu, 2010-07-15 at 08:08 +0800, Raymond Yau wrote:
> > > >>
> > > >>>> I posted both of those bug reports. Honestly, I just want it to work
> > > >>>> without all the error output to syslog and thrashing of my HD for
> > > >>>> minutes at a time. As I said, I've got the output of pulseaudio
> > -vvvvv
> > > >>>> if anyone would like to look at it and tell me what I need to do to
> > fix
> > > >>>> the problem.
> > > >>>>
> > > >>>> Chris
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>> Just upload your current pulseaudio.log and output of alsa-info.sh to
> > > >>> mandriva 's bugzilla
> > > >>>
> > > >>> Cannot obtain any conclusion based on the log which you have posted
> > last
> > > >>> year ( xmms)
> > > >>>
> > > >>> as Jaroslav Kysela said , need the real system time between I/O
> > operations
> > > >>> and you'll see if it's issue in the ALSA driver or a task scheduling
> > > >>> problem.
> > > >>
> > > >> Here is the bug report with the outputs uploaded.
> > > >>
> > > >> https://qa.mandriva.com/show_bug.cgi?id=60169
> > > >
> > > > Well seeing as my process when getting such a bug is to report it here
> > > > on behalf of the user, I suspect that this has reached a stalemate....
> > >
> > > Please, provide also /var/log/messages output for xrun_debug=11 - see
> > > http://www.alsa-project.org/main/index.php/XRUN_Debug for more details.
> > We
> > > can detect the ALSA ring buffer issues in this way, too.
> > >
> > > Jaroslav
> > >
> > See pastebin file http://pastebin.com/MdENbSNd
> > Hopefully I did this correctly.
> >
> >
> You have to provide the PA server log since we just want to know how PA
> server handle the underrun condition when the PA client use small buffer
> size
>
> Did "aplay -Dhw:0,0 --buffer-size=128 any.wav" get underrun
I'll check, how the heck to I stop xrun_debug from running???
--
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-16 0:24 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 [this message]
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
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=1279239851.12171.1.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).