intel-media-va-driver VPP broken until 22.6.5

[Tim Kelsall]

[ Impact ]

See https://github.com/intel/media-driver/issues/1662 for bug filed against upstream Intel media-driver project.

The version of intel-media-va-driver on Jammy has broken functionality in the VPP path.
This can be worked around by replacing with intel-media-va-driver-non-free.

The root cause is that free EU kernel shaders were not updated before 22.6.5, causing the vaCreateContext call to fail with the VAEntrypointVideoProc entry point.

[ Test Plan ]

TODO - Tim please fill in

[ Where problems could occur ]

Anywhere in hardware-accelerated video decode/encoding for Intel CPUs when the "free" driver "intel-media-driver" is installed.

[ Other Info ]

None.

[Tim Kelsall (tykel)]

Additionally I see intel-media-driver on https://tracker.debian.org/pkg/intel-media-driver has a 23.1.1 stable backport for Debian Bullseye. [https://packages.debian.org/bullseye-backports/intel-media-va-driver]

Could we update to this version?

[James Henstridge (jamesh)]

I also ran into a problem with missing VA-API post processing support on Lunar. I filed it as bug 2019917 since Lunar ships a version that includes the purported fix mentioned in the Github issue, and I'm unsure if it is actually the same problem.

[Tim Kelsall (tykel)]

Hello Ubuntu maintainers,

Are there any pending items I can help with to move this along?

[Daniel van Vugt (vanvugt)]

Strictly speaking this should be "Fix Released" since Ubuntu 23.04 and later ships the 23 driver already.

You should see a nominate for series link near the top of the page so please select that to nominate this bug to be fixed in jammy.

P.S. We recommend intel-media-va-driver-non-free because it has more features and is consistently better maintained by Intel.

[Tim Kelsall (tykel)]

Hi Daniel,

I am not a Ubuntu bug supervisor so I do not have a "nominate for series" link (found this out via https://answers.launchpad.net/launchpad/+question/140509). If you are, could you please help out, or rope in someone who can?

About intel-media-va-driver-non-free: This is the workaround we currently recommend. But as you can imagine getting all end-users to change this on their endpoint is non-trivial.

[Daniel van Vugt (vanvugt)]

Actually bug controllers don't get the nominate for series link because we get a "Target for series" link instead. Which means the nomination was accepted. But the problem is that accepting it and creating a jammy task also requires the task have an owner - someone assigned to do the backporting. So I won't be doing that right now without someone first volunteering to own the work. I know this is convoluted and potentially irritating but it is the process we have.

The number of similar bugs in this situation that are fixed in Ubuntu-next but not yet in the most recent LTS is non-trivial. I don't have any stats but this is a common situation so I don't want to make an exception here when we potentially have more important bugs that could be backported to jammy. Any bug fix _can_ be backported immediately, just so long as someone is volunteering to own the task.

[Daniel van Vugt (vanvugt)]

The first step would be to identify what to backport to jammy. If the answer is:

https://github.com/intel/media-driver/commit/469f8c9f0d497320772629c912464018da653876

then it's quite large so needs to be discussed with the kernel team who manage hardware enablement.

[Tim Kelsall (tykel)]

That would be the commit to include in the backport, yes.

I am happy to help with the work. Please give me details about how to involve said kernel team, thanks!