Re: [pulseaudio-discuss] pulseaudio debug mode
'Twas brillig, and Chris at 26/07/10 23:40 did gyre and gimble: 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. http://pastebin.com/tZNYaqRV OK, I'll prepare some packages for you so that we can start to isolate what queue it is that is causing the problem. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio debug mode
On Tue, 2010-07-27 at 08:37 +0100, Colin Guthrie wrote: 'Twas brillig, and Chris at 26/07/10 23:40 did gyre and gimble: 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. http://pastebin.com/tZNYaqRV OK, I'll prepare some packages for you so that we can start to isolate what queue it is that is causing the problem. Col Thanks Colin, looking forward to them. Chris -- Chris KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
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, 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. http://pastebin.com/tZNYaqRV -- Chris KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio debug mode
On Fri, Jul 23, 2010 at 03:04:01AM CEST, Chris wrote: What is the best way to start PA for debugging and still have all the usual clients running? You are probably best off to run pulseaudio in a terminal with - specified on the command-line. This will give you a rather verbose log of what pulseaudio is doing. Then just pipe the data to a file for later analysis. You may also need to turn pulseaudio autospawning off to prevent pulseaudio automatically starting again when you kill it to be run in a terminal. Luke ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio debug mode
On 2010-07-23 03:04, Chris wrote: What is the best way to start PA for debugging and still have all the usual clients running? pacmd set-log-level 4 ...if your log target is set to syslog, just watch it grow :-) -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] pulseaudio debug mode
What is the best way to start PA for debugging and still have all the usual clients running? -- Chris KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
