Re: [pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.

2010-02-04 Thread PulseAudio
#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--+-
  Reporter:  PaulePanter  |   Owner:  lennart
  Type:  defect   |  Status:  new
 Milestone:   |   Component:  daemon 
Resolution:   |Keywords: 
--+-

Comment(by PaulePanter):

 Replying to [comment:11 PaulePanter]:

 […]

 {{{
 $ pulseaudio -k # `autospawn = 0` in `~/.pulse/client.conf`
 $ LANG=C pulseaudio -v # `gnome-volume-control` started in other
 terminal. ConsoleKit messages removed.
 […]
 I: alsa-source.c: Increasing wakeup watermark to 361.50 ms
 W: ratelimit.c: 52071 events suppressed
 D: memblock.c: Pool full
 D: memblock.c: Pool full
 D: memblock.c: Pool full
 D: memblock.c: Pool full
 I: alsa-source.c: Overrun!
 […]
 }}}

 […]

 I searched for this error message on the WWW and did get some responses
 that this might be related to the ALSA driver. Can you confirm that?

 I added the following options to load with the `snd_hda_intel` module.

 {{{
 $ more /etc/modprobe.d/snd-hda-intel.conf
 options snd_hda_intel position_fix=1
 }}}

 No starting `gnome-volume-manager` does not give a high CPU load anymore
 and behaves as expected. The problem now is, when there is high load on
 the system as opening an application the audio is not useable anymore
 (strange noises instead of music in MPlayer for example) and the
 application needs to be restarted.

 I also find the following in the output `dmesg`.

 {{{
 $ dmesg
 […]
 [ 3625.517773] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517794] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517814] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517835] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517856] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517877] hda-intel: spurious response 0xe0160:0x0, last cmd=0x1f0004
 [ 3625.517898] hda-intel: spurious response 0x1:0x0, last cmd=0x1f0004
 [ 3625.517919] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517940] hda-intel: spurious response 0x0:0x0, last cmd=0x1f0004
 [ 3625.517960] hda-intel: spurious response 0x20025:0x0, last cmd=0x1f0004
 }}}

 Is that a known problem? Is my only option to report this to the ALSA
 guys?

-- 
Ticket URL: http://pulseaudio.org/ticket/758#comment:12
PulseAudio http://pulseaudio.org/
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.

2010-01-20 Thread PulseAudio
#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--+-
  Reporter:  PaulePanter  |   Owner:  lennart
  Type:  defect   |  Status:  new
 Milestone:   |   Component:  daemon 
Resolution:   |Keywords: 
--+-

Comment(by PaulePanter):

 Replying to [comment:1 lennart]:
  A per symbol breakdown would be good.

 With the great help in the #oprofile IRC channel I was told that you maybe
 need the output of `oprofile -l`. You can find the full output in
 [http://de.pastebin.ca/1759464 pastebin]. Here is an excerpt.

 {{{
 $ oprofile -l
 [ warnings ]
 CPU: AMD64 processors, speed 1800 MHz (estimated)
 Counted CPU_CLK_UNHALTED events (Cycles outside of halt state) with a unit
 mask of 0x00 (No unit mask) count 10
 samples  %image name   app name symbol
 name
 707224   20.0892  libpulsecore-0.9.21.so   libpulsecore-0.9.21.so
 peaks_resample
 579277   16.4548  libpulsecore-0.9.21.so   libpulsecore-0.9.21.so
 remap_channels_matrix_c
 383113   10.8826  libpulsecore-0.9.21.so   libpulsecore-0.9.21.so
 pa_sconv_s16le_to_float32ne
 1964775.5811  libc-2.10.2.so   libc-2.10.2.so   memcpy
 1019822.8969  libc-2.10.2.so   libc-2.10.2.so   memset
 53118 1.5089  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 do_something
 46831 1.3303  libpthread-2.10.2.so libpthread-2.10.2.so
 pthread_mutex_lock
 39875 1.1327  libdbus-1.so.3.4.0   libdbus-1.so.3.4.0
 /lib/libdbus-1.so.3.4.0
 35026 0.9949  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_memblock_unref
 28470 0.8087  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 __i686.get_pc_thunk.bx
 25617 0.7277  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_flist_pop
 23618 0.6709  libxaa.solibxaa.so
 /usr/lib/xorg/modules/libxaa.so
 23385 0.6643  libpthread-2.10.2.so libpthread-2.10.2.so
 pthread_mutex_unlock
 23029 0.6542  oprofiledoprofiled
 /usr/bin/oprofiled
 22709 0.6451  libpthread-2.10.2.so libpthread-2.10.2.so
 __pthread_mutex_unlock_usercnt
 22080 0.6272  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_flist_push
 21888 0.6217  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 enable_mainloop_sources
 20619 0.5857  libglib-2.0.so.0.2200.4  libglib-2.0.so.0.2200.4
 g_main_context_prepare
 18747 0.5325  libglib-2.0.so.0.2200.4  libglib-2.0.so.0.2200.4
 g_main_context_check
 18574 0.5276  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_memblockq_push
 18368 0.5218  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 callback
 17780 0.5051  gnome-volume-control.pulse gnome-volume-control.pulse
 /usr/bin/gnome-volume-control.pulse
 17264 0.4904  libpulse.so.0.12.2   libpulse.so.0.12.2
 pa_mainloop_dispatch
 15501 0.4403  libasound.so.2.0.0   libasound.so.2.0.0
 /usr/lib/libasound.so.2.0.0
 14998 0.4260  [vdso] (tgid:29071 range:0xf77e-0xf77e1000) gnome-
 volume-control.pulse [vdso] (tgid:29071 range:0xf77e-0xf77e1000)
 14866 0.4223  libxcb.so.1.1.0  libxcb.so.1.1.0
 /usr/lib/libxcb.so.1.1.0
 14781 0.4199  libpthread-2.10.2.so libpthread-2.10.2.so
 __i686.get_pc_thunk.bx
 14624 0.4154  libpulse-mainloop-glib.so.0.0.4 libpulse-mainloop-
 glib.so.0.0.4 /usr/lib/libpulse-mainloop-glib.so.0.0.4
 14614 0.4151  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_pstream_ref
 13719 0.3897  libc-2.10.2.so   libc-2.10.2.so
 __i686.get_pc_thunk.bx
 13635 0.3873  libpulsecore-0.9.21.so   libpulsecore-0.9.21.so
 pa_resampler_run
 13379 0.3800  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_run_once
 13233 0.3759  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_iochannel_is_readable
 10810 0.3071  libglib-2.0.so.0.2200.4  libglib-2.0.so.0.2200.4
 g_main_context_iterate
 10782 0.3063  libpixman-1.so.0.16.4libpixman-1.so.0.16.4
 /usr/lib/libpixman-1.so.0.16.4
 10339 0.2937  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_once_begin
 10052 0.2855  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_memblock_ref
 9931  0.2821  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_iochannel_read_with_creds
 9907  0.2814  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_pstream_unref
 9843  0.2796  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_mcalign_pop
 9817  0.2789  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_queue_pop
 9815  0.2788  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_memchunk_reset
 9612  0.2730  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 pa_memblock_release
 9174  0.2606  libpulsecommon-0.9.21.so libpulsecommon-0.9.21.so
 fix_current_read
 9115  

Re: [pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.

2010-01-15 Thread PulseAudio
#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--+-
  Reporter:  PaulePanter  |   Owner:  lennart
  Type:  defect   |  Status:  new
 Milestone:   |   Component:  daemon 
Resolution:   |Keywords: 
--+-

Comment(by PaulePanter):

 Replying to [comment:8 PaulePanter]:
  Replying to [comment:3 PaulePanter]:
   Replying to [comment:2 PaulePanter]:
Replying to [comment:1 lennart]:
 A per symbol breakdown would be good.
   
What options do I have to pass to `opreport` to get such a symbol
 breakdown?
   
I searched for this »oprofile symbol breakdown« and the hits did
 not contain any information on what options to use. Reading the manual
 page (`man opreport`) and searching for »symbol« also just brought the
 `-l` option to my attention.
  
   I just read HowToUseOProfile again were it says in step 5 »Generate a
 per-symbol break down of the profile data:« to use `opreport -l
 /usr/bin/pulseaudio` whose output I provided in my report. Or did I do
 anything wrong. I have the package with debug symbols installed
 (pulseaudio-dbg 0.9.21-1).
 
  Could you please point me to some instruction on how to generate the
 information you need.

 Thanks to Ford_Perfect on the IRC channel, it was pointed out to me, that
 there seems to be some problems with the debugging symbols. I try to
 straighten this out [1] and will submit the OProfile symbol breakdown
 afterward.

 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565373

-- 
Ticket URL: http://pulseaudio.org/ticket/758#comment:9
PulseAudio http://pulseaudio.org/
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`. (was: High CPU load with `gnome-volume-control.pulse`.)

2010-01-14 Thread PulseAudio
#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--+-
  Reporter:  PaulePanter  |   Owner:  lennart
  Type:  defect   |  Status:  new
 Milestone:   |   Component:  daemon 
Resolution:   |Keywords: 
--+-

Comment(by PaulePanter):

 I am able to reproduce this with `pavucontrol` too. I therefore adapted
 the summary.

 {{{
 $ dpkg -l pavucontrol
 […]
 ii  pavucontrol0.9.9-1PulseAudio Volume Control
 }}}

-- 
Ticket URL: http://pulseaudio.org/ticket/758#comment:4
PulseAudio http://pulseaudio.org/
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets


Re: [pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.

2010-01-14 Thread PulseAudio
#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--+-
  Reporter:  PaulePanter  |   Owner:  lennart
  Type:  defect   |  Status:  new
 Milestone:   |   Component:  daemon 
Resolution:   |Keywords: 
--+-

Comment(by lennart):

 BTW. as a side note: it is expected that PA's PCU usage increases when
 pavucontrol/g-v-c runs, since for volume meters on screen we decrease the
 latency of the audio devices so that what you hear and what you see is
 neatly in sync. Lower latencies automatically mean higher CPU usage.

 So, you can expect something like 30% or so in the worst case, which
 multiplies if you have many cards.

-- 
Ticket URL: http://pulseaudio.org/ticket/758#comment:6
PulseAudio http://pulseaudio.org/
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets