Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Justin Piszcz]

Hi,

 

Bug report:

 

==> /var/log/user.log <==

May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
ALSA woke us up to write new data to the device, but there was actually
nothing to write!

May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
Most likely this is a bug in the ALSA driver '(null)'. Please report this
issue to the ALSA developers.

May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c: We
were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
returned 0 or another value < min_avail.

 

$ uname -a

Linux atom 3.14.0 #2 SMP Wed Apr 2 06:30:21 EDT 2014 x86_64 GNU/Linux

 

$ lsusb

Bus 002 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Bus 002 Device 008: ID 0baf:0303 U.S. Robotics 

Bus 002 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port

Bus 002 Device 010: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse

Bus 002 Device 009: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard

Bus 002 Device 006: ID 413c:1002 Dell Computer Corp. Keyboard Hub

Bus 002 Device 005: ID 0d8c:0008 C-Media Electronics, Inc. 

Bus 002 Device 003: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Justin.

Re: Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Raymond Yau]

>
>
>
> Bug report:
>

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers

You have to provide pulseaudio verbose log, output of alsa-info.sh ,  lsusb
-vvvv  and step to reproduce your problem when you report the bug

>
>
> ==> /var/log/user.log <==
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> ALSA woke us up to write new data to the device, but there was actually
> nothing to write!
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> Most likely this is a bug in the ALSA driver '(null)'. Please report this
> issue to the ALSA developers.

Name of alsa sink seem changed from USB-audio to null,  did you find any
unplug event if USB audio device in system log

Any error message related to USB controllers and your audio card

>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
We
> were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
> returned 0 or another value < min_avail.
>
>

Re: Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Justin Piszcz]

Hello,

 

As requested—

 

http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt

http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt

http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt

 

Ø  step to reproduce your problem when you report the bug

 

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.

 

Justin.

 

From: Raymond Yau [mailto:superquad.vortex2@gmail.com] 
Sent: Thursday, May 29, 2014 10:15 PM
To: Justin Piszcz
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

 

>
>
>
> Bug report:
>

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers

You have to provide pulseaudio verbose log, output of alsa-info.sh ,  lsusb -vvvv  and step to reproduce your problem when you report the bug

>
>
> ==> /var/log/user.log <==
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> ALSA woke us up to write new data to the device, but there was actually
> nothing to write!
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> Most likely this is a bug in the ALSA driver '(null)'. Please report this
> issue to the ALSA developers.

Name of alsa sink seem changed from USB-audio to null,  did you find any unplug event if USB audio device in system log

Any error message related to USB controllers and your audio card

>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c: We
> were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
> returned 0 or another value < min_avail.
>
>

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Raymond Yau]

>
>
>
> As requested—
>
>
>
> http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt
>
> http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt

Your log is useless

You have to change log-info=debug in daemon.conf and restart pulseaudio

https://bugzilla.redhat.com/show_bug.cgi?id=1065097

>
> http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt

USB Mixer: usb_id=0x0d8c0008, ctrlif=0, ctlerr=0
Card: C-Media USB Audio Device at usb-0000:00:1d.0-1.1.1, full speed
  Unit: 9
    Control: name="Speaker Playback Volume", index=0
    Info: id=9, control=2, cmask=0x3, channels=2, type="S16"
    Volume: min=-7264, max=-16, dBmin=-2837, dBmax=-6

your USB audio device are unlikely to provide 28.31/7248 dB per step

http://www.freedesktop.org/wiki/Software/PulseAudio/Backends/ALSA/Decibel/

If hardware volume control always less than  0dB
Pulseaudio need to use software volume (GAIN) for  PA_VOLUME_NORM when
volume slider is at maximum, software volume need rewind of audio data in
sound card buffer for recalulation when you change volume slider

>
> Ø  step to reproduce your problem when you report the bug
>
>
>
> 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.
>
>


https://bugs.freedesktop.org/show_bug.cgi?id=46236

The workaround seem to use ignore_dB=1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: [alsa-devel] Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Raymond Yau]

[-- Attachment #1.1: Type: text/plain, Size: 2465 bytes --]

>
>
>
> As requested—
>
>
>
> http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt
>
> http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt

>
> http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt
>

control.6 {
iface MIXER
name 'Speaker Playback Volume'
value.0 151
value.1 151
comment {
access 'read write'
type INTEGER
count 2
range '0 - 151'
dbmin -2837
dbmax -6
dbvalue.0 -6
dbvalue.1 -6
}
}

You have to specify log_info=debug in daemon.conf

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

>
>
> Ø  step to reproduce your problem when you report the bug

>
> 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.
>

> > ==> /var/log/user.log <==
> >
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
alsa-sink.c:
> > ALSA woke us up to write new data to the device, but there was actually
> > nothing to write!
> >
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
alsa-sink.c:
> > Most likely this is a bug in the ALSA driver '(null)'. Please report
this
> > issue to the ALSA developers.
>
> Name of alsa sink seem changed from USB-audio to null,  did you find any
unplug event if USB audio device in system log
>
> Any error message related to USB controllers and your audio card
>
> >
> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
alsa-sink.c: We
> > were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
> > returned 0 or another value < min_avail.
> >
> >

http://www.alsa-project.org/main/index.php/XRUN_Debug

/proc/asound/card#/pcm0p/xrun_debug

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).

# Enable basic debugging and dump stack, check hardware pointer on the
period update
# Usefull to just see, if PCM stream is stopped for a reason (usually wrong
audio process timing from scheduler)
# And to check the values from driver
echo 11 > /proc/asound/card0/pcm0p/xrun_debug

[-- Attachment #1.2: Type: text/html, Size: 3254 bytes --]

[-- Attachment #2: Type: text/plain, Size: 186 bytes --]

_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

Re: Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA

[Justin Piszcz]

On Sat, May 31, 2014 at 12:58 AM, Raymond Yau
<superquad.vortex2@gmail.com> wrote:
>
>>
>>
>>
>> As requested—
>>
>>
>>
>> http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt
>>
>> http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt
>
>>
>> http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt
>>
>
> control.6 {
> iface MIXER
> name 'Speaker Playback Volume'
> value.0 151
> value.1 151
> comment {
> access 'read write'
> type INTEGER
> count 2
> range '0 - 151'
> dbmin -2837
> dbmax -6
> dbvalue.0 -6
> dbvalue.1 -6
> }
> }
>
> You have to specify log_info=debug in daemon.conf
>
> 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
>
>>
>>
>> Ø  step to reproduce your problem when you report the bug
>
>>
>> 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.
>>
>
>> > ==> /var/log/user.log <==
>> >
>> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
>> > alsa-sink.c:
>> > ALSA woke us up to write new data to the device, but there was actually
>> > nothing to write!
>> >
>> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
>> > alsa-sink.c:
>> > Most likely this is a bug in the ALSA driver '(null)'. Please report
>> > this
>> > issue to the ALSA developers.
>>
>> Name of alsa sink seem changed from USB-audio to null,  did you find any
>> unplug event if USB audio device in system log
>>
>> Any error message related to USB controllers and your audio card
>>
>> >
>> > May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio]
>> > alsa-sink.c: We
>> > were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
>> > returned 0 or another value < min_avail.
>> >
>> >
>
> http://www.alsa-project.org/main/index.php/XRUN_Debug
>
> /proc/asound/card#/pcm0p/xrun_debug
>
> 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).
>
> # Enable basic debugging and dump stack, check hardware pointer on the
> period update
> # Usefull to just see, if PCM stream is stopped for a reason (usually wrong
> audio process timing from scheduler)
> # And to check the values from driver
> echo 11 > /proc/asound/card0/pcm0p/xrun_debug

Thanks, if I can reproduce it- I will try this, so far I have not been
able to get it to recur.

Regards,

Justin.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel