All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Hupfer <liam@hpfr.net>
To: alsa-devel@alsa-project.org
Subject: Pulseaudio dropping GPU audio
Date: Sat, 24 Jul 2021 16:50:09 -0500	[thread overview]
Message-ID: <87fsw3l6o5.fsf@hpfr.net> (raw)

Hello,

I’ve set up a Linux VM where I’m passing through an RX 580. I’m using the GPU
audio and my monitor’s audio jack. For some reason the Linux VM keeps losing
track of the audio output. It always shows up under `lspci' under ID `06:00.0'
using the `snd_hda_intel' driver, but `pulseaudio' (I also tried `pipewire',
same issue) keep losing it. Most times I can restart `pulseaudio' and it will
find the device again; occasionally, it takes multiple restarts.

I checked the Arch wiki and I found something[¹] on audio over HDMI (I’m using
DisplayPort, if that matters). I checked the device and it did report `Enable+'.
Even so, I added the kernel parameter `snd_hda_intel.enable_msi=1', but nothing
changed.

Here are some `journalctl --user -u pulseaudio' logs:
┌────
│ 20:37:31 host pulseaudio[2373]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
│ 20:37:31 host pulseaudio[2373]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
│ 20:37:31 host pulseaudio[2373]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
└────

Anyone have any suggestions for troubleshooting? `pulseaudio'’s logs suggested
it might have to do with ALSA, so I asked for help here.

Thank you!

—Liam


[¹] <https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Slowed_down_audio_pumped_through_HDMI_on_the_video_card>

             reply	other threads:[~2021-07-24 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 21:50 Liam Hupfer [this message]
2021-07-27 16:30 ` Pulseaudio dropping GPU audio Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsw3l6o5.fsf@hpfr.net \
    --to=liam@hpfr.net \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.