[X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

Bug #1928996 reported by Samuel Ainsworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
New
Undecided
Unassigned

Bug Description

Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs.

I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: skainswo 2282708 F.... pulseaudio
 /dev/snd/controlC0: skainswo 2282708 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 19 16:08:41 2021
InstallationDate: Installed on 2020-05-15 (369 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/home/username/.nix-profile/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: skainswo 2282708 F.... pulseaudio
 /dev/snd/controlC0: skainswo 2282708 F.... pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago)
dmi.bios.date: 04/20/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: X58A-UD3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Samuel Ainsworth (sidekick) wrote :
Revision history for this message
Samuel Ainsworth (sidekick) wrote :

As a quick update, I managed to kill all of the spurious pulseaudio processes that had been lying around as a result of `pulseaudio -k && pulseaudio --start` and got the systemd pulseaudio process back on its feet. Then I confirmed that the audio worked, suspended my system, and woke it up again and the audio still works!

Therefore I suspect that pulseaudio processes started by the user in terminal sessions (daemonized) do not survive the suspend/resume cycle for some reason(?). How the systemd pulseaudio process failed to begin with remains the larger issue, however.

Revision history for this message
Samuel Ainsworth (sidekick) wrote :

Just woke up from a suspend once again and still getting this issue. The most recent log lines are

May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Starting Sound Service...
May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Started Sound Service.
May 19 17:30:27 skainswo-X58A-UD3R pulseaudio[1811]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

But these logs are from two days ago...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.