<p><br>
><br>
> <br>
><br>
> As requested—<br>
><br>
> <br>
><br>
> <a href="http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt">http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt</a><br>
><br>
> <a href="http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt">http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt</a></p>
<p>><br>
> <a href="http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt">http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt</a><br>
></p>
<p>control.6 {<br>
iface MIXER<br>
name 'Speaker Playback Volume'<br>
value.0 151<br>
value.1 151<br>
comment {<br>
access 'read write'<br>
type INTEGER<br>
count 2<br>
range '0 - 151'<br>
dbmin -2837<br>
dbmax -6<br>
dbvalue.0 -6<br>
dbvalue.1 -6<br>
}<br>
}</p>
<p>You have to specify log_info=debug in daemon.conf</p>
<p>Check the pulseaudio debug log whether pulseaudio calculated software volume is accurate enough (VOLUME_ACCURACY=PA_VOLUME_NORM/100) since your Max dB -0.06 are quite close to PA_VOLUME_NORM</p>
<p>> <br>
><br>
> Ø step to reproduce your problem when you report the bug</p>
<p>><br>
> I often SSH to my machine or use X remotely and not locally— this is the first time I have seen this in logs that I can remember and I’ve not changed anything locally.<br>
></p>
<p>> > ==> /var/log/user.log <==<br>
> ><br>
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:<br>
> > ALSA woke us up to write new data to the device, but there was actually<br>
> > nothing to write!<br>
> ><br>
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:<br>
> > Most likely this is a bug in the ALSA driver '(null)'. Please report this<br>
> > issue to the ALSA developers.<br>
><br>
> Name of alsa sink seem changed from USB-audio to null, did you find any unplug event if USB audio device in system log<br>
><br>
> Any error message related to USB controllers and your audio card<br>
><br>
> ><br>
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c: We<br>
> > were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()<br>
> > returned 0 or another value < min_avail.<br>
> ><br>
> ></p>
<p><a href="http://www.alsa-project.org/main/index.php/XRUN_Debug">http://www.alsa-project.org/main/index.php/XRUN_Debug</a></p>
<p>/proc/asound/card#/pcm0p/xrun_debug</p>
<p>Replace '#' with your card number (usually 0). This proc file can enable various debugging tools. The CONFIG_SND_PCM_XRUN_DEBUG, CONFIG_SND_VERBOSE_PROCFS, CONFIG_SND_DEBUG options must be enabled in your kernel (if xrun_debug proc file is present - this feature is enabled).</p>
<p># Enable basic debugging and dump stack, check hardware pointer on the period update<br>
# Usefull to just see, if PCM stream is stopped for a reason (usually wrong audio process timing from scheduler)<br>
# And to check the values from driver<br>
echo 11 > /proc/asound/card0/pcm0p/xrun_debug<br>
</p>