[Bug]: Firefox/Netflix/Fedora 37 doesn't use video acceleration

[Jamstah]

Which component impacted?

Decode

Is it regression? Good in old configuration?

This is a new configuration so I couldn't say

What happened?

1. Installed intel-media-driver (rpmfusion)
2. Disabled av1 in Firefox
3. Play video in youtube
4. Check intel_gpu_top and see video acceleration in use
5. Play video in netflix
6. Check intel_gpu_top and see no video acceleration in use

Raising here because it looks right in the firefox logs - both sites seem to successfully initialise the va-api decoder.

youtube:

[RDD 268046: MediaSupervisor #2]: D/PlatformDecoderModule FFVPX: FFmpegVideoDecoder::FFmpegVideoDecoder MIME video/vp9 Codec ID 167
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Initialising VA-API FFmpeg decoder
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   Format vp9 is accelerated
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   codec vp9 : Google VP9
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
...
[AVHWDeviceContext @ 0x7f90abb36d80] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 22.5.4 ().
[AVHWDeviceContext @ 0x7f90abb36d80] Driver not found in known nonstandard list, using standard behaviour.
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   VA-API FFmpeg init successful

netflix:

[RDD 268046: MediaSupervisor #4]: D/PlatformDecoderModule FFVPX: FFmpegVideoDecoder::FFmpegVideoDecoder MIME video/vp9 Codec ID 167
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Initialising VA-API FFmpeg decoder
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   Format vp9 is accelerated
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   codec vp9 : Google VP9
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0

[AVHWDeviceContext @ 0x7f90abb36e00] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 22.5.4 ().
[AVHWDeviceContext @ 0x7f90abb36e00] Driver not found in known nonstandard list, using standard behaviour.
[RDD 268046: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX:   VA-API FFmpeg init successful

What's the usage scenario when you are seeing the problem?

Playback, Web browser

What impacted?

Video acceleration

Debug Information

jammy:~$ rpm -qa | grep libva
libva-2.16.0-1.fc37.x86_64
libva-utils-2.16.0-1.fc37.x86_64
libva-intel-driver-2.4.1-9.fc37.x86_64
jammy:~$ rpm -qa | grep intel-media-driver
intel-media-driver-22.5.4-1.fc37.x86_64
jammy:~$ ls /dev/dri
by-path  card0  card1  renderD128  renderD129
jammy:~$ vainfo
Trying display: wayland
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.5.4 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileNone                   :	VAEntrypointStats
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointFEI
      VAProfileH264Main               :	VAEntrypointEncSliceLP
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointFEI
      VAProfileH264High               :	VAEntrypointEncSliceLP
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointFEI
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointFEI
      VAProfileHEVCMain               :	VAEntrypointEncSliceLP
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile1            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileVP9Profile3            :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointEncSlice
      VAProfileHEVCMain422_10         :	VAEntrypointVLD
      VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
      VAProfileHEVCMain422_12         :	VAEntrypointVLD
      VAProfileHEVCMain422_12         :	VAEntrypointEncSlice
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_12         :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain10          :	VAEntrypointVLD
      VAProfileHEVCSccMain10          :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444         :	VAEntrypointVLD
      VAProfileHEVCSccMain444         :	VAEntrypointEncSliceLP
      VAProfileAV1Profile0            :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointEncSliceLP

With trace - output for trying youtube or netflix is exactly the same:

jammy:tmp$ cat libva_trace.log.131346.thd-0x00043510 
[10506.639665][ctx       none]==========va_TraceInitialize
[10506.639668][ctx       none]=========vaInitialize ret = VA_STATUS_SUCCESS, success (no error) 
[10506.639672][ctx       none]=========vaQueryConfigProfiles ret = VA_STATUS_SUCCESS, success (no error) 
[10506.639674][ctx       none]=========vaQueryConfigEntrypoints ret = VA_STATUS_SUCCESS, success (no error) 
[10506.639676][ctx       none]==========va_TraceCreateConfig
[10506.639676][ctx       none]	profile = 6, VAProfileH264Main
[10506.639676][ctx       none]	entrypoint = 1, VAEntrypointVLD
[10506.639677][ctx       none]	num_attribs = 0
[10506.639682][ctx       none]=========vaCreateConfig ret = VA_STATUS_SUCCESS, success (no error) 
[10506.639682][ctx       none]==========va_TraceDestroyConfig
[10506.639682][ctx       none]	config = 0x00000000
[10506.639684][ctx       none]=========vaDestroyConfig ret = VA_STATUS_SUCCESS, success (no error) 
[10506.640028][ctx       none]==========va_TraceTerminate
[10506.640030][ctx       none]=========vaTerminate ret = VA_STATUS_SUCCESS, success (no error) 

Do you want to contribute a patch to fix the issue?

If I knew what I was doing I'd be happy to but I expect its beyond my knowledge :)

[eero-t]

On which HW this is on?

[Jamstah]

Lenovo P51 with Optimus. The Intel part is Intel Corporation TigerLake-H GT1

jammy:~$ sudo lspci
[sudo] password for jammy: 
00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05)
00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05)
00:07.1 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #1 (rev 05)
00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05)
00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05)
00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11)
00:16.3 Serial controller: Intel Corporation Device 43e3 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 43b8 (rev 11)
00:1c.4 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #5 (rev 11)
00:1c.5 PCI bridge: Intel Corporation Device 43bd (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 43bf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #9 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4389 (rev 11)
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-H SPI Controller (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation TU117GLM [T1200 Laptop GPU] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
04:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5407
05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
0a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
0b:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-LM (rev 03)

[eero-t]

Optimus part sounds suspicious. Maybe those applications are just using the wrong video driver, or maybe Fusion package is disabling support for whatever codec Netflix tries to use in browser?

I think you should file this bug against Fedora, and its Firefox (or Fusion driver) package.

[Jamstah]

Looking at the logs they are both using vp9 and both going through the same vaapi interface, which is why I raised it here.

Is there a way to trace what input the media-driver is getting? To raise the bug elsewhere I'd need some sort of evidence to show that media-driver is being driven differently (ie incorrectly) in one case or the other.

[eero-t]

Looking at the logs they are both using vp9 and both going through the same vaapi interface, which is why I raised it here.

Is there a way to trace what input the media-driver is getting? To raise the bug elsewhere I'd need some sort of evidence to show that media-driver is being driven differently (ie incorrectly) in one case or the other.

I'm not involved with media-driver development, but maybe @dvrogozh could help?

[XinfengZhang]

LIBVA_TRACE could help to dump the input of media_driver. you could use this env variable.

[Jamstah]

I think that's what I used above, but I can see its not clear. When I get a chance I'll go again with a trace from youtube and a trace from netflix.

[Jamstah]

Trace output appears the same when I try netflix or youtube - does the example in the description look like the full trace data to you or am I missing some output somewhere?

[XinfengZhang]

if you want more logs in media driver
please refer:
https://github.com/intel/media-driver/wiki/Video-Processing-Debug-Tool#how-to-dump-vp-hlt-log
you also could get parameters and dumps by
https://github.com/intel/media-driver/wiki/Decode-and-Encode-Debug-Tool-and-surface-dump

and from the log you attached:
[10506.639665][ctx none]==========va_TraceInitialize
[10506.639668][ctx none]=========vaInitialize ret = VA_STATUS_SUCCESS, success (no error)
[10506.639672][ctx none]=========vaQueryConfigProfiles ret = VA_STATUS_SUCCESS, success (no error)
[10506.639674][ctx none]=========vaQueryConfigEntrypoints ret = VA_STATUS_SUCCESS, success (no error)
[10506.639676][ctx none]==========va_TraceCreateConfig
[10506.639676][ctx none] profile = 6, VAProfileH264Main
[10506.639676][ctx none] entrypoint = 1, VAEntrypointVLD
[10506.639677][ctx none] num_attribs = 0
[10506.639682][ctx none]=========vaCreateConfig ret = VA_STATUS_SUCCESS, success (no error)
[10506.639682][ctx none]==========va_TraceDestroyConfig
[10506.639682][ctx none] config = 0x00000000
[10506.639684][ctx none]=========vaDestroyConfig ret = VA_STATUS_SUCCESS, success (no error)
[10506.640028][ctx none]==========va_TraceTerminate
[10506.640030][ctx none]=========vaTerminate ret = VA_STATUS_SUCCESS, success (no error)

it just create one H264 decode config, nothing valuable.

it is why I want full LIBVA log. because there are some negotiation process, and also real context creation.