[jammy] VA-API doesn't work on DCN 3.1.4

[Mario Limonciello]

[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

The device ID was included in upstream mesa 22.3.1.

[ Test Plan ]

 * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
 * Verify that '# vainfo' shows the correct information.

[ Where problems could occur ]

 * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths.
 * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases.

[ Other Info ]
* It can be cherry picked with this single commit:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

* AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works.

[Andreas Hasenack (ahasenack)]

Hello Mario, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Anson Tsao (ansontsao)]

Looks positive on my end with mesa proposed

[Launchpad Janitor (janitor)]

This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2

---------------
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium

  * patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
  * patches: Fix a freeze with iris under stress test. (LP: #1990089)
  * patches: Revert two commits causing kwin to eventually crash. (LP:
    #2003339)

 -- Timo Aaltonen <email address hidden> Fri, 21 Apr 2023 14:51:10 +0300

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!