Re: [qubes-users] [3.2rc2] Pulseaudio 100% CPU load at dom0
On 09/02/2016 07:10 PM, entr0py wrote: David Hobach: On 08/31/2016 08:14 PM, entr0py wrote: Eva Star: 3.2rc2 - clean install (on 3.2rc1 with updates I do not have this problem) At dom0 pulseaudio proccess always eat 100% of CPU. If I kill it, then it starts again! Please, help. Hot to fix this issue or how to disable pulseaudio start after kill. Same problem here, only by updating though. Had similar symptoms on Qubes 3.1. If you have multiple audio adapters (ie Onboard + HDMI), disable one. (On KDE, it was PulseAudio Volume Control > Configuration. Don't know XFCE.) I also have multiple (incl. external). Disconnecting the external one does not appear to help though. Pulseaudio child processes constantly die and get started again, i.e. the PID is changing every 1-2s. I guess that's not normal? Sound in VMs is stuttering. rsyslogd also eats quite a lot of CPU, but I bet it's due to the pulse logs. Sample log and /etc/pulse/default.pa attached. Anyone got an idea? In my case, the Onboard and HDMI adapters kept trying to connect, kicking out the other adapter. The machine would basically lock up every few seconds and CPU would max out. Same symptoms as you describe with the PIDs. What I did specifically was go to Configuration tab and set Profile to 'Off'. One of the dom0 updates caused this setting to revert to its default. Perhaps you've got another adapter besides the USB, or the machine keeps looking for the disconnected adapter? You were 100% right. In my case I had connected a new GPU which had registered itself as new audio output device (HDMI) and apparently kept pulseaudio busy. For reference: Non-KDE users can pop up a dom0 console and use the "systemsettings" command to get into the GUI. There you can go to Multimedia -> Audio Hardware setup and switch the unneeded sound cards off (Profile = off). -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6a679e42-b36a-10ca-c06d-40e48e2a1689%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. smime.p7s Description: S/MIME Cryptographic Signature
Re: [qubes-users] [3.2rc2] Pulseaudio 100% CPU load at dom0
David Hobach: > On 08/31/2016 08:14 PM, entr0py wrote: >> Eva Star: >>> 3.2rc2 - clean install (on 3.2rc1 with updates I do not have this >>> problem) >>> >>> At dom0 pulseaudio proccess always eat 100% of CPU. If I kill it, >>> then it starts again! Please, help. Hot to fix this issue or how >>> to disable pulseaudio start after kill. > > Same problem here, only by updating though. > >> Had similar symptoms on Qubes 3.1. If you have multiple audio >> adapters (ie Onboard + HDMI), disable one. (On KDE, it was >> PulseAudio Volume Control > Configuration. Don't know XFCE.) > > I also have multiple (incl. external). Disconnecting the external one > does not appear to help though. > > Pulseaudio child processes constantly die and get started again, i.e. > the PID is changing every 1-2s. I guess that's not normal? Sound in > VMs is stuttering. > > rsyslogd also eats quite a lot of CPU, but I bet it's due to the > pulse logs. > > Sample log and /etc/pulse/default.pa attached. > > Anyone got an idea? In my case, the Onboard and HDMI adapters kept trying to connect, kicking out the other adapter. The machine would basically lock up every few seconds and CPU would max out. Same symptoms as you describe with the PIDs. What I did specifically was go to Configuration tab and set Profile to 'Off'. One of the dom0 updates caused this setting to revert to its default. Perhaps you've got another adapter besides the USB, or the machine keeps looking for the disconnected adapter? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/31a88ccf-899f-1748-385f-ff90b5d3b778%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [3.2rc2] Pulseaudio 100% CPU load at dom0
On 08/31/2016 08:14 PM, entr0py wrote: Eva Star: 3.2rc2 - clean install (on 3.2rc1 with updates I do not have this problem) At dom0 pulseaudio proccess always eat 100% of CPU. If I kill it, then it starts again! Please, help. Hot to fix this issue or how to disable pulseaudio start after kill. Same problem here, only by updating though. Had similar symptoms on Qubes 3.1. If you have multiple audio adapters (ie Onboard + HDMI), disable one. (On KDE, it was PulseAudio Volume Control > Configuration. Don't know XFCE.) I also have multiple (incl. external). Disconnecting the external one does not appear to help though. Pulseaudio child processes constantly die and get started again, i.e. the PID is changing every 1-2s. I guess that's not normal? Sound in VMs is stuttering. rsyslogd also eats quite a lot of CPU, but I bet it's due to the pulse logs. Sample log and /etc/pulse/default.pa attached. Anyone got an idea? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8ded276e-db56-ef34-b44e-62c09fc928e6%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. #!/usr/bin/pulseaudio -nF # # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software Foundation, # Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. # This startup script is used only if PulseAudio is started per-user # (i.e. not in system mode) .nofail ### Load something into the sample cache #load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav #load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-access /usr/share/sounds/generic.wav .fail ### Automatically restore the volume of streams and devices load-module module-device-restore load-module module-stream-restore load-module module-card-restore ### Automatically augment property information from .desktop files ### stored in /usr/share/application load-module module-augment-properties ### Should be after module-*-restore but before module-*-detect load-module module-switch-on-port-available ### Load audio drivers statically ### (it's probably better to not load these drivers manually, but instead ### use module-udev-detect -- see below -- for doing this automatically) #load-module module-alsa-sink #load-module module-alsa-source device=hw:1,0 #load-module module-null-sink #load-module module-pipe-sink ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif ### Automatically connect sink and source if JACK server is present .ifexists module-jackdbus-detect.so .nofail load-module module-jackdbus-detect channels=2 .fail .endif ### Automatically load driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif ### Load several protocols .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix ### Network access (may be configured with paprefs, so leave this commented ### here if you plan to use paprefs) #load-module module-esound-protocol-tcp #load-module module-native-protocol-tcp #load-module module-zeroconf-publish ### Load the RTP receiver module (also configured via paprefs, see above) #load-module module-rtp-recv ### Load the RTP sender module (also configured via paprefs, see above) #load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Sink'" #load-module module-rtp-send source=rtp.monitor ### Load additional modules from GConf settings. This can be configured with the paprefs tool. ### Please keep in mind that the modules configured by paprefs might conflict with manually ### loaded modules. .ifexists module-gconf.
Re: [qubes-users] [3.2rc2] Pulseaudio 100% CPU load at dom0
Eva Star: > 3.2rc2 - clean install (on 3.2rc1 with updates I do not have this problem) > > At dom0 pulseaudio proccess always eat 100% of CPU. > If I kill it, then it starts again! > Please, help. Hot to fix this issue or how to disable pulseaudio start after > kill. > Had similar symptoms on Qubes 3.1. If you have multiple audio adapters (ie Onboard + HDMI), disable one. (On KDE, it was PulseAudio Volume Control > Configuration. Don't know XFCE.) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1451b40-159c-608a-8868-405dd4125441%40gmail.com. For more options, visit https://groups.google.com/d/optout.
