[pulseaudio-discuss] pulseaudio debug mode

Chris cpollock at embarqmail.com
Mon Jul 26 15:40:25 PDT 2010

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, the link below is for some more debug output. Notice in the first
section that 8 seconds after spamd starts processing a message the the
Alsa error starts, 2 seconds after that the overruns start. Notice in
line 145 that it took 145 seconds to process a message, that's about 125
too long. I've noticed that when I start getting the overrun errors that
the processing of a message takes forever, though this doesn't happen
every time, just periodically. All I know is that while this is going on
the drive is constantly being accessed for minutes at a time in the
first case from 9:03 to 9:08.


KeyID 0xE372A7DA98E6705C

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20100726/b948983c/attachment.pgp>

More information about the pulseaudio-discuss mailing list