HDMI output with More than one child device for port B in VBT error

[AceLan Kao]

[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.

[You-Sheng Yang (vicamo)]

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1017.17 kernel in https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed2 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17

---------------
linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync update-dkms-versions helper

  * CVE-2023-3269
    - exec: Remove FOLL_FORCE for stack setup
    - mm: introduce new 'lock_mm_and_find_vma()' page fault helper
    - mm: make the page fault mmap locking killable
    - arm64/mm: Convert to using lock_mm_and_find_vma()
    - powerpc/mm: Convert to using lock_mm_and_find_vma()
    - mips/mm: Convert to using lock_mm_and_find_vma()
    - riscv/mm: Convert to using lock_mm_and_find_vma()
    - arm/mm: Convert to using lock_mm_and_find_vma()
    - mm/fault: convert remaining simple cases to lock_mm_and_find_vma()
    - powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma()
    - mm: make find_extend_vma() fail if write lock not held
    - execve: expand new process stack manually ahead of time
    - mm: always expand the stack with the mmap write lock held
    - [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA

  * CVE-2023-3389
    - io_uring/poll: serialize poll linked timer start with poll removal

  * amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
    (LP: #2025670)
    - platform/x86/amd/pmf: Register notify handler only if SPS is enabled

  * Mute/mic LEDs no function on some HP Platforms (LP: #2025444)
    - ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on EliteBook

  * Various backlight issues with the 6.0/6.1 kernel (LP: #2023638)
    - ACPI: video: Stop trying to use vendor backlight control on laptops from
      after ~2012

  * HDMI output with More than one child device for port B in VBT error
    (LP: #2025195)
    - SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10

 -- You-Sheng Yang <email address hidden> Wed, 12 Jul 2023 11:26:03 +0800

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 6.5.0-5.5

---------------
linux (6.5.0-5.5) mantic; urgency=medium

  * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23)

 -- Andrea Righi <email address hidden> Wed, 06 Sep 2023 15:51:04 +0200

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~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-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-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!