@Ubuntu Kernel Bot, I can not find any logic in your statement : "If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed." (Beneath, a bug can be solved or not, but to close a bug, what is this ?)
And also 8 duplicated bug reports will be closed ? After closing the bug reports, which strategy you have, to solve the bug ? Do you expect that Ubuntu user shall write again a bug-report with the given Issue ? I agree with Ivanto (comment 75): "Ubuntu Jammy 22.04 LTS Enable proposed There is no kernel 5.19.0-41.42" -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe2320000 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe2260000 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~~~~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:2b:00.1/sound/card0/input17 snd_hda_intel 0000:2b:00.1: bound 0000:2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel 0000:2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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
