This bug is awaiting verification that the linux- azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.
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. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+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
