[Bug 300154] [regression] no sound via HDMI on Kaby Lake
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 300154] [regression] no sound via HDMI on Kaby Lake"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 300154] [regression] no sound via HDMI on Kaby Lake"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 300154] [regression] no sound via HDMI on Kaby Lake"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 27 Oct 2026 20:32:48 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300154
Bug ID: 300154
Summary: [regression] no sound via HDMI on Kaby Lake
Product: Base System
Version: 16.0-CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: glebius@FreeBSD.org
Created attachment 276573
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=276573&action=edit
dmesg with verbose boot
My X1 Carbon 7th Gen lost audio output via HDMI. Unfortunately, I don't
exercise this functionality often, thus I can't tell how recent the regression
is. I guess it is somewhere between summer 2025 and summer 2026.
Booted with 'boot -v' and with HDMI cable plugged in, dmesg.boot.txt attached.
Switched hw.snd.default_unit=1. sndctl and mixer output attached. Trying
playback - no sound produced and not messages in dmesg. Went through sleep &
resume cycle - no changes.
However, at previous boot, without HDMI cable plugged in and without 'boot -v',
after plugging in the HDMI cable and trying playback I was
seeing messages in dmesg:
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20220011 timeout on
address 2
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20270d01 timeout on
address 2
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20270610 timeout on
address 2
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20272d01 timeout on
address 2
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20373400 timeout on
address 2
Oct 27 13:09:25 <kern.crit> think kernel: hdac0: Command 0x20373411 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f2 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f3 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f4 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f5 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f6 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x203734f7 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x20370740 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x20373000 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x20373200 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x20373000 timeout on
address 2
Oct 27 13:09:26 <kern.crit> think kernel: hdac0: Command 0x20373100 timeout on
address 2
Oct 27 13:09:30 <kern.crit> think syslogd: last message repeated 31 times
--
You are receiving this mail because:
You are the assignee for the bug.