[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
HDMI video does not work for me on this kernel. 5.19.0-31 works fine. I'm running ubuntu DISTRIB_RELEASE=22.10 on and HP Fury 16 G9 laptop with 12th Gen Intel(R) Core(TM) i9-12950HX. It also causes the fan to come on. Logging in is very slugging. 5.19.0.31 is very responsive and does not force the fan on under casual use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug 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/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :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 :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-signed-hwe-5.19/+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
[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
Ubuntu 20.04.5 LTS xen-hypervisor-4.11-amd64 4.11.3+24-g14b62ab3e5-1ubuntu2.3 Reverted back to kernel 5.4.0-135 and bridging with Xen VMs is working again. Spent the day trying to work out why bridging suddenly stopped working. Guest is 18.04.6 LTS. I'm pretty sure that under 137, the path cost was 100 for enp6s0f0, instead of the 19 it shows now. brctl showstp xenbr1 xenbr1 bridge id 8000.90e2ba065da8 designated root8000.90e2ba065da8 root port 0path cost 0 max age 20.00 bridge max age20.00 hello time2.00 bridge hello time 2.00 forward delay15.00 bridge forward delay 15.00 ageing time 300.00 hello timer 0.00 tcn timer 0.00 topology change timer 0.00 gc timer 230.64 flags enp6s0f0 (1) port id8001stateforwarding designated root8000.90e2ba065da8 path cost 19 designated bridge 8000.90e2ba065da8 message age timer 0.00 designated port8001forward delay timer0.00 designated cost 0hold timer 0.00 flags vif1.0 (2) port id8002stateforwarding designated root8000.90e2ba065da8 path cost100 designated bridge 8000.90e2ba065da8 message age timer 0.00 designated port8002forward delay timer0.00 designated cost 0hold timer 0.00 flags -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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
