Re: [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode]

From: Chris <cpollock@embarqmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode]
Date: Sun, 25 Jul 2010 20:30:04 -0500	[thread overview]
Message-ID: <1280107804.29411.1.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimj3W_tgi-+Qqgz-J31u-daOqJ8a2E74qEUzy8U@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1895 bytes --]

On Mon, 2010-07-26 at 07:31 +0800, Raymond Yau wrote:
> 2010/7/26 Chris <cpollock@embarqmail.com>
> 
> > Raymond, attached is a post I made today to the pulseaudio list.
> >
> > From: Chris <cpollock@embarqmail.com>
> > To: pulseaudio-discuss@mail.0pointer.de
> > Date: Sun, 25 Jul 2010 12:15:02 -0500
> > Subject: Re: [pulseaudio-discuss] pulseaudio debug mode
> > On Fri, 2010-07-23 at 08:58 +0100, Colin Guthrie wrote:
> > > 'Twas brillig, and Chris at 23/07/10 02:04 did gyre and gimble:
> > > > What is the best way to start PA for debugging and still have all the
> > > > usual clients running?
> > >
> > > If you mean having all the clients connect (e.g. applications with
> > > libcanberra support or similar for sound events), then there are
> > > basically two ways.
> > >
> > > The first is as Luke suggests. These clients will automatically
> > > reconnect to PA if they need to (provided you have a vaguely recent
> > > libcanberra), after it is restarted and run in debug mode.
> > >
> > > Alternatively you can simply set debug-level to "debug" in daemon.conf
> > > (in /etc/pulse or ~/.pulse), and then "grep pulseaudio /var/log/messages"
> > >
> > > Col
> > >
> >
> > Colin, link below is for debug output also some other output. Anything
> > look out of place that would cause the overruns?
> >
> > http://pastebin.com/ZWSWmXZt
> > --
> >
> 
> Most likely you will need to set debug-level to "debug" in daemon.conf
> logout and login , and check the /var/log/messages
> 
> I suspect it occur after PA server abort and auto spawn , so please don't
> just post the PA log starting from "asyncq overrun" , you need to post from
> the last two PA startup sequence before the error occur since we need to
> know why PA auto spawn

Is this what you mean Raymond:
http://pastebin.com/4RT7YaG6


-- 
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