Bug #1873641 “pulseaudio says: ALSA woke us up to write new data...” : Bugs : linux package : Ubuntu

Revision history for this message

John Gilmore (gnu-gilmore) wrote on 2020-04-19:

#1

AlsaInfo.txt Edit (58.1 KiB, text/plain; charset="utf-8")
AudioDevicesInUse.txt Edit (300 bytes, text/plain; charset="utf-8")
CRDA.txt Edit (468 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (92.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.6 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (597 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (719 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (16.5 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (10.9 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (11.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.1 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (36.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (270.2 KiB, text/plain; charset="utf-8")

Revision history for this message

John Gilmore (gnu-gilmore) wrote on 2020-04-19:

#2

Um, that should say I got a "single" report like this in syslog so far.

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2020-04-19: Status changed to Confirmed

#3

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Antti Palsola (antti.palsola) wrote on 2020-05-19:

#4

Download full text (9.0 KiB)

This happens also to me with my M-Audio Fast Track Ultra (yes, I know it is an old device but it has worked until now) after upgrading from Ubuntu 19.10 to 20.04 LTS. (Did not have any issues with 19.10.) My motherboard is Asus Prime X570-P AM4.

$ systemctl status --user pulseaudio.service
● pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2020-05-19 13:27:58 EEST; 17min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 2209 (pulseaudio)
     CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
             └─2209 /usr/bin/pulseaudio --daemonize=no --log-target=journal

May 19 13:27:54 [HOSTNAME MASKED] systemd[2202]: Starting Sound Service...
May 19 13:27:58 [HOSTNAME MASKED] systemd[2202]: Started Sound Service.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA

Excerpts from /var/log/syslog:
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA
---- [Power off – power on cycle on M-Audio Fast Track Ultra] ----
May 19 13:29:27 [HOSTNAME MASKED] kernel: [ 194.584035] usb 3-3: USB disconnect, device number 2
May 19 13:29:30 [HOSTNAME MASKED] kernel: [ 197.207250] usb 3-3: new high-speed USB device number 5 using xhci_hcd
May 19 13:29:30 [HOSTNAME MASKED] kernel: [ 197.233340] usb 3-3: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8
May 19 13:29:30 [HOSTNAME MASKED] kernel: [ 197.233343] usb 3-3: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid...

This happens also to me with my M-Audio Fast Track Ultra (yes, I know it is an old device but it has worked until now) after upgrading from Ubuntu 19.10 to 20.04 LTS. (Did not have any issues with 19.10.) My motherboard is Asus Prime X570-P AM4.

$ systemctl status --user pulseaudio.service
● pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2020-05-19 13:27:58 EEST; 17min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 2209 (pulseaudio)
     CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
             └─2209 /usr/bin/pulseaudio --daemonize=no --log-target=journal

May 19 13:27:54 [HOSTNAME MASKED] systemd[2202]: Starting Sound Service...
May 19 13:27:58 [HOSTNAME MASKED] systemd[2202]: Started Sound Service.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA

Excerpts from /var/log/syslog:
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA
---- [Power off – power on cycle on M-Audio Fast Track Ultra] ----
May 19 13:29:27 [HOSTNAME MASKED] kernel: [  194.584035] usb 3-3: USB disconnect, device number 2
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.207250] usb 3-3: new high-speed USB device number 5 using xhci_hcd
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.233340] usb 3-3: config 1 interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.233343] usb 3-3: config 1 interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234455] usb 3-3: New USB device found, idVendor=0763, idProduct=2080, bcdDevice= 1.51
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234457] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234458] usb 3-3: Product: Fast Track Ultra
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234459] usb 3-3: Manufacturer: M-Audio
May 19 13:29:30 [HOSTNAME MASKED] mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-3"
May 19 13:29:30 [HOSTNAME MASKED] mtp-probe: bus: 3, device: 5 was not an MTP device
May 19 13:29:30 [HOSTNAME MASKED] systemd[2202]: Reached target Sound Card.
May 19 13:29:30 [HOSTNAME MASKED] systemd[1385]: Reached target Sound Card.
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.083958] usb 3-3: set quirks for FTU Effect Feedback/Volume
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.098203] usb 3-3: set quirk for FTU Effect Duration
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.099701] usb 3-3: set quirks for FTU Effect Feedback/Volume
May 19 13:29:32 [HOSTNAME MASKED] mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-3"
May 19 13:29:32 [HOSTNAME MASKED] mtp-probe: bus: 3, device: 5 was not an MTP device
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.489446] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.490200] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.490973] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.491700] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.492448] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.494447] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.495193] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.495948] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.496819] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.497694] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.499701] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.500447] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.501194] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.502074] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.502945] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.505070] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.505944] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.506698] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.507571] usb 3-3: Unable to change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.508449] usb 3-3: Unable to change format on ep #81: already in use

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$ uname -a
Linux [HOSTNAME MASKED] 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy pulseaudio alsa-base alsa-utils
pulseaudio:
  Installed: 1:13.99.1-1ubuntu3.2
  Candidate: 1:13.99.1-1ubuntu3.2
  Version table:
 *** 1:13.99.1-1ubuntu3.2 500
        500 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:13.99.1-1ubuntu3 500
        500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
        500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        500 http://fi.archive.ubuntu.com/ubuntu focal/main i386 Packages
        100 /var/lib/dpkg/status
alsa-utils:
  Installed: 1.2.2-1ubuntu1
  Candidate: 1.2.2-1ubuntu1
  Version table:
 *** 1.2.2-1ubuntu1 500
        500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Ultra [Fast Track Ultra], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALCS1200A Analog [ALCS1200A Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 1: ALCS1200A Digital [ALCS1200A Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Revision history for this message

Antti Palsola (antti.palsola) wrote on 2020-05-19:

#5

I got the sound working after trying the following fixes stated in <https://askubuntu.com/questions/1230363/20-04-internal-speaker-audio-is-not-working-in-ubuntu-20-04-lts-after-upgradi>:
- sudo alsa force-reload
- sudo apt install pavucontrol
- sudo apt install alsa-tools-gui and setting jack_detect = no
- timidity-daemon was already not installed

Revision history for this message

Alessio Prini (alessioprini) wrote on 2021-01-10:

#6

I'm also experiencing several crash.
I'm using an Asus PRIME B450M-A II motherboard.

$ systemctl status --user pulseaudio.service
pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-01-10 20:55:22 CET; 25min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 1474 (pulseaudio)
     CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
             └─1474 /usr/bin/pulseaudio --daemonize=no --log-target=journal

gen 10 20:55:22 XXX systemd[1468]: Starting Sound Service...
gen 10 20:55:22 XXX systemd[1468]: Started Sound Service.
gen 10 20:55:26 XXX pulseaudio[1474]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
gen 10 20:55:26 XXX pulseaudio[1474]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
gen 10 20:55:26 XXX pulseaudio[1474]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
gen 10 20:55:47 XXX pulseaudio[1474]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

$ uname -a
Linux XXX 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Christian Castelli (voodoo81people) wrote on 2021-04-14:

#7

Also got the same error in journalctl:

---
● pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2021-04-14 06:43:42 CEST; 2h 20min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 1277 (pulseaudio)
     CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
             └─1277 /usr/bin/pulseaudio --daemonize=no --log-target=journal

apr 14 06:43:41 thecastles systemd[1271]: Starting Sound Service...
apr 14 06:43:42 thecastles systemd[1271]: Started Sound Service.
apr 14 08:59:35 thecastles pulseaudio[1277]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
apr 14 08:59:35 thecastles pulseaudio[1277]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
apr 14 08:59:35 thecastles pulseaudio[1277]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

---

However, I didn't experience any issue with audio.

Linux 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 20.04.2

Ubuntu
linux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package