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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873641

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to 
the device, but there was actually nothing to write.
  Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA 
driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
  Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- 
however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

  I'm running Ubuntu 20.04 beta, and have just gotten past several crash
  or abort issues in pulseaudio on this Gigabyte AX370-Gaming5
  motherboard.  With tonight's update to:

  Package: pulseaudio
  Architecture: amd64
  Version: 1:13.99.1-1ubuntu3

  and the running kernel:

  Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42
  UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  I got a somg;e report like this in syslog (so far).  Since the
  developers asked me to report it, here's the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-24-generic 5.4.0-24.28
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 03:24:07 2020
  InstallationDate: Installed on 2020-04-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IwConfig:
   enp6s0    no wireless extensions.
   
   enp5s0    no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic 
root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware                            1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to