From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: HDMI card is marked "off" on system resume and stays so until reset
Date: Thu, 24 Jul 2025 16:05:20 +0200 (CEST) [thread overview]
Message-ID: <1855350181c58300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18553501818cf200-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #465 was opened from j39m:
(Continued from [Pipewire issue 4809](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4809).)
# Basic Symptoms
When resuming, my device often fails to continue playback over my HDMI output. Higher-level utils (`pavucontrol`, `pw-dump`, etc.) report that the corresponding "sink" is not present (until I reset the output).
Pipewire dev `@pvir` read my logs thusly:
<details>
<summary>`alsactl monitor` and `amixer`</summary>
Last state update after resume:
```
2025-07-24 22:15:16,844: alsactl
node hw:0, #7 (0,0,0,HDMI/DP,pcm=7 Jack,0) VALUE
2025-07-24 22:15:16,854: amixer
numid=7,iface=CARD,name='HDMI/DP,pcm=7 Jack'
; type=BOOLEAN,access=r-------,values=1
: values=off
```
The next update then comes only when workaround is run:
```
2025-07-24 22:16:02,772: alsactl
node hw:0, #12 (3,7,0,ELD,0) VALUE INFO
2025-07-24 22:16:02,781: amixer
numid=7,iface=CARD,name='HDMI/DP,pcm=7 Jack'
; type=BOOLEAN,access=r-------,values=1
: values=on
```
It appears there was no notification for the off->on transition, or the off->on only happens when doing the workaround cycling displays, so probably this is ALSA or HDMI bug.
</details>
I haven't tried waiting longer than this, but I assume that if ALSA thinks the card is still gone ~45s after resume, it's already a bit too far gone to be worried about exact timing.
# System readout
<details>
```
[j39m@flaglock6 ~/Downloads/tmp]
$ rpm -q alsa-lib intel-audio-firmware
alsa-lib-1.2.14-3.fc42.x86_64
intel-audio-firmware-20250708-1.fc42.noarch
[j39m@flaglock6 ~/Downloads/tmp]
$ inxi -A
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
Audio driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
driver: snd_pci_acp3x
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
driver: snd_hda_intel
API: ALSA v: k6.15.6-200.fc42.x86_64 status: kernel-api
Server-1: PipeWire v: 1.4.6 status: active
```
</details>
Issue URL : https://github.com/alsa-project/alsa-lib/issues/465
Repository URL: https://github.com/alsa-project/alsa-lib
parent reply other threads:[~2025-07-24 14:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18553501818cf200-webhooks-bot@alsa-project.org>]
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=1855350181c58300-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).