#1019194 pulseaudio: ALSA woke us up to write new data to the device, but there was actually nothing to write.

Package:
pulseaudio
Source:
pulseaudio
Description:
PulseAudio sound server
Submitter:
Tobias Koeck
Date:
2022-11-30 09:15:03 UTC
Severity:
normal
#1019194#5
Date:
2022-09-05 10:04:12 UTC
From:
To:
Dear Maintainer,

found in /var/log/syslog

Sep  5 11:58:46 tron-nb pulseaudio[4602]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Sep  5 11:58:46 tron-nb pulseaudio[4602]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
Sep  5 11:58:46 tron-nb pulseaudio[4602]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
#1019194#10
Date:
2022-11-30 09:11:49 UTC
From:
To:
On Mon, 05 Sep 2022 12:04:12 +0200 Tobias Koeck <tkoeck@imap.a2gb.de>
wrote:> Package: pulseaudio
 >
 > Sep 5 11:58:46 tron-nb pulseaudio[4602]: ALSA woke us up to write new
data to the device, but there was actually nothing to write.
 > Sep 5 11:58:46 tron-nb pulseaudio[4602]: Most likely this is a bug in
the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA
developers.
 > Sep 5 11:58:46 tron-nb pulseaudio[4602]: We were woken up with
POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or
another value < min_avail.

I'm seeing something similar here, in a QEMU virtual machine started
with -device intel-hda -device hda-duplex. The only difference with the
logs reported by Tobias above is the alsa driver in second line:

Nov 30 03:53:00 debian pulseaudio[600]: ALSA woke us up to write new
data to the device, but there was actually nothing to write.
Nov 30 03:53:00 debian pulseaudio[600]: Most likely this is a bug in the
ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA
developers.
Nov 30 03:53:00 debian pulseaudio[600]: We were woken up with POLLOUT
set -- however a subsequent snd_pcm_avail() returned 0 or another value
< min_avail.