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

[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 -vvvvv # `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