[alsa-devel] [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode]
cpollock at embarqmail.com
Mon Jul 26 03:30:04 CEST 2010
On Mon, 2010-07-26 at 07:31 +0800, Raymond Yau wrote:
> 2010/7/26 Chris <cpollock at embarqmail.com>
> > Raymond, attached is a post I made today to the pulseaudio list.
> > From: Chris <cpollock at embarqmail.com>
> > To: pulseaudio-discuss at 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:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20100725/e8268e41/attachment-0001.sig
More information about the Alsa-devel