Open Bug 1776362 Opened 2 years ago Updated 1 year ago

[X11/Intel/NVIDIA] Failed to use DRM device for video decoding when NVIDIA proprietary drivers are installed on secondary GFX card

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Version:
Firefox 101
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
REOPENED

People

(Reporter: dednev, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(8 files)

additional firefox and system information (hardware info, vaapi info, etc.)
20.20 KB, application/zip
Details
about:support data for firefox 102
36.04 KB, text/plain
Details
about-support-103a1.txt
36.14 KB, text/plain
Details
about:support data from another PC with Intel G10 graphics and modesetting xorg driver
34.27 KB, text/plain
Details
about:support data with only MOZ_X11_EGL set for 102b9
35.77 KB, text/plain
Details
about:support for firefox 102b9 with modesetting driver, X11_EGL and no MOZ_DRM*
36.64 KB, text/plain
Details
firefox-20230526.log
17.45 KB, text/x-log
Details
firefox-20230526-no-errors.log
361.15 KB, text/x-log
Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

I'm trying to get accelerated video decoding for YouTube and similar sites.
I'm using Firefox 101.0.1 on Debian, lsb_release -a output:
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

If I start firefox with Dmabuf debug information, I've got following error messages while trying to play YouTube videos:
MOZ_LOG="Dmabuf:5" firefox

[Child 27538: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 27538: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied
[Child 27621: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 27621: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied

But I've all permissions for reported device, ls -lR /dev/dri gives:
/dev/dri:
total 0
drwxr-xr-x 2 root root 80 Jun 24 08:37 by-path
crw-rw----+ 1 makc users 226, 0 Jun 24 08:37 card0
crw-rw----+ 1 makc users 226, 128 Jun 24 08:37 renderD128

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Jun 24 08:37 pci-0000:00:02.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jun 24 08:37 pci-0000:00:02.0-render -> ../renderD128

My user name is makc, group users and I've all needed permissions for this.

I've tried to play h.264 video with VLC and it works perfectly. As I can see with intel_gpu_top
it uses accelerated video decoding (VAAPI) and Video load graph is greater than 0%.

But firefox think that it has no permissions to access DRI device. So I suppose that there is some bug,
that prevents firefox from usinb DRI and accelerated video decoding (VAAPI).

Actual results:

Accelerated video decoding doesn't work and I've got following error messages on console with enabled debugging output:

[Child 27538: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 27538: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied
[Child 27621: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 27621: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied

Expected results:

Accelerated video decoding and intel_gpu_top showing Video graph greater than 0%

Blocks: egl-linux-dmabuf
Component: Untriaged → Graphics
Product: Firefox → Core

Thanks for the report. /dev/dri/card0 is definitely not what we want to use here - /dev/dri/renderD128 is what we'd expect. Just to be sure: you don't have the MOZ_DRM_DEVICE env variable set to /dev/dri/card0?

"version": "101.0.1",
"updateChannel": "release",

VAAPI has been fixed in 102 (currently Beta). Just setting media.ffmpeg.vaapi.enabled to true and restarting Firefox should be enough with 102.
VAAPI is enabled by default for https://nightly.mozilla.org.

"MOZ_DRM_DEVICE": "/dev/dri/card0",
"MOZ_WAYLAND_DRM_DEVICE": "/dev/dri/card0",

Please remove these environment variables.

"gfx.webrender.enabled": true,
"media.av1.enabled": false,
"media.ffmpeg.vaapi-drm-display.enabled": true,
"media.ffmpeg.vaapi.enabled": true,
"media.ffvpx.enabled": false,
"media.rdd-process.enabled": false,
"media.rdd-vpx.enabled": false,
"media.webm.enabled": false,

Please reset these prefs back to their default.

Install this addon to disable codecs that are not supported by your GPU: https://addons.mozilla.org/firefox/addon/enhanced-h264ify/
Note: VP9 and AV1 are required for resolutions above 1080p.

"adapterVendorID2": "0x10de",

Ideally please uninstall the proprietary Nvidia driver.

bug 1771382 has been fixed in 103: With 103, VAAPI might work in Intel-only mode even if the proprietary Nvidia driver is installed.

(In reply to Robert Mader [:rmader] from comment #1)

Thanks for the report. /dev/dri/card0 is definitely not what we want to use here - /dev/dri/renderD128 is what we'd expect. Just to be sure: you don't have the MOZ_DRM_DEVICE env variable set to /dev/dri/card0?

I've tried to set MOZ_DRM_DEVICE=/dev/dri/renderD128 with exactly the same result. So, setting this variable to /dev/dri/card0 or /dev/dri/renderD128doesn't make any difference for me. Moreover, with MOZ_DRM_DEVICE unset Firefox tries to use /dev/dri/card0, not /dev/dri/renderD128. But as I can see with lsof my VLC uses both of these devices.

(In reply to Darkspirit from comment #2)

"version": "101.0.1",
"updateChannel": "release",

VAAPI has been fixed in 102 (currently Beta). Just setting media.ffmpeg.vaapi.enabled to true and restarting Firefox should be enough with 102.
VAAPI is enabled by default for https://nightly.mozilla.org.

Thanks, I'll try it soon.

"MOZ_DRM_DEVICE": "/dev/dri/card0",
"MOZ_WAYLAND_DRM_DEVICE": "/dev/dri/card0",

Please remove these environment variables.

I've tried to remove them, this doesn't make sense. Dri card device open error still here with me.

"gfx.webrender.enabled": true,
"media.av1.enabled": false,
"media.ffmpeg.vaapi-drm-display.enabled": true,
"media.ffmpeg.vaapi.enabled": true,
"media.ffvpx.enabled": false,
"media.rdd-process.enabled": false,
"media.rdd-vpx.enabled": false,
"media.webm.enabled": false,

Please reset these prefs back to their default.

I've tried to start firefox in safe mode and as I understand those variables are in default state while running safe mode. But VAAPI doesn't work anyway.

Install this addon to disable codecs that are not supported by your GPU: https://addons.mozilla.org/firefox/addon/enhanced-h264ify/
Note: VP9 and AV1 are required for resolutions above 1080p.

I've tried to install this extension, but I can't find any changes in firefox video decoding behaviour.

"adapterVendorID2": "0x10de",

Ideally please uninstall the proprietary Nvidia driver.

bug 1771382 has been fixed in 103: With 103, VAAPI might work in Intel-only mode even if the proprietary Nvidia driver is installed.

I'll try to uninstall Nvidia driver, but Google Chrome works in such configuration perfectly after providing it with proper command line argument to disable gpu blacklisting and enable VAAPI video decoding.

Seeing comment 2 it probably makes sense if you try nightly and check if things work there (it will also use a clean profile). There's been a bunch of fixes lately.

(In reply to Darkspirit from comment #2)

"version": "101.0.1",
"updateChannel": "release",

VAAPI has been fixed in 102 (currently Beta). Just setting media.ffmpeg.vaapi.enabled to true and restarting Firefox should be enough with 102.
VAAPI is enabled by default for https://nightly.mozilla.org.

I've tried both 102 and 103a1 with exactly the same result: VAAPI acceleration doesn't work even if media.ffmpeg.vaapi.enabled is set to true. More over I've got following error messages on console while trying to play video on YouTube:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Child 15911: Main Thread]: D/Dmabuf We're missing DRM render device!
[Child 15911: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[Child 15911: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[2022-06-26T18:28:33Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:28:33Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:28:33Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:28:33Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[RDD 16008: Main Thread]: D/Dmabuf We're missing DRM render device!
[RDD 16008: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 16008: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[Utility AudioDecoder 16016: Main Thread]: D/Dmabuf We're missing DRM render device!
[Utility AudioDecoder 16016: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[Utility AudioDecoder 16016: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0

If I set environment variables MOZ_X11_EGL=1 and MOZ_DRM_DEVICE=/dev/dri/card0 I've got different error messages while trying to play same video:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Parent 17095: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Parent 17095: Main Thread]: D/Dmabuf nsDMABufDevice::Configure()
[Parent 17095: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 17095: Main Thread]: D/Dmabuf DMABuf is enabled
[Parent 17095: Main Thread]: D/Dmabuf VAAPIGetAcceleratedProfiles()
libva info: VA-API version 1.10.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[Parent 17095: Main Thread]: D/Dmabuf   Initialised VAAPI connection: version 1.10
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile H264ConstrainedBaseline:
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile H264Main:
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile H264High:
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile VP8Version0_3:
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile VP9Profile0:
[Parent 17095: Main Thread]: D/Dmabuf   Supported profile VP9Profile2:
[Child 17271: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 17271: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied
[Child 17271: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[Child 17271: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[2022-06-26T18:33:38Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:33:38Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:33:38Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:33:38Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[RDD 17371: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[RDD 17371: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 17371: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[Utility AudioDecoder 17386: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Utility AudioDecoder 17386: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied
[Utility AudioDecoder 17386: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[Utility AudioDecoder 17386: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

"Permission denied" for /dev/dri/card0 still here with me.
More information in attached about:support output for versions I've tried to test.

(In reply to dednev from comment #8)

"windowLayerManagerType": "WebRender (Software)",
"windowLayerManagerRemote": true,
"adapterDescription": "Mesa Intel(R) HD Graphics 620 (KBL GT2)",
"adapterVendorID": "0x8086",
"adapterDeviceID": "0x5916",
"adapterRAM": 0,
"adapterDrivers": "",
"driverVendor": "mesa/iris",
"driverVersion": "20.3.5.0",
"driverDate": "",
"adapterVendorID2": "0x10de",
"adapterDeviceID2": "0x134e",

VAAPI is enabled by default in Nightly for Mesa >= 21.
You have outdated Mesa 20, you need to set:
gfx.x11-egl.force-enabled=true
gfx.webrender.all=true
media.ffmpeg.vaapi.enabled=true

Hehe, alright, the issue most likely is a totally different one: FEATURE_FAILURE_DDX_INTEL. The Intel DDX/Xorg driver is so broken that we disable Webrender altogether. Once you uninstall it and switch to the modesetting driver, things should start to just work.

(In reply to Darkspirit from comment #9)

VAAPI is enabled by default in Nightly for Mesa >= 21.
You have outdated Mesa 20, you need to set:
gfx.x11-egl.force-enabled=true
gfx.webrender.all=true
media.ffmpeg.vaapi.enabled=true

"Permission denied" for /dev/dri/card0 still here, but I've also got new LibVA initialization errors:

$ MOZ_LOG="Dmabuf:5" ./firefox 
[Parent 20084: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Parent 20084: Main Thread]: D/Dmabuf nsDMABufDevice::Configure()
[Parent 20084: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 20084: Main Thread]: D/Dmabuf DMABuf is enabled
[Parent 20084: Main Thread]: D/Dmabuf VAAPIGetAcceleratedProfiles()
libva info: VA-API version 1.10.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[Parent 20084: Main Thread]: D/Dmabuf   Initialised VAAPI connection: version 1.10
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile H264ConstrainedBaseline:
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile H264Main:
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile H264High:
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile VP8Version0_3:
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile VP9Profile0:
[Parent 20084: Main Thread]: D/Dmabuf   Supported profile VP9Profile2:
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Child 20262: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Child 20262: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Отказано в доступе
[Child 20262: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[Child 20262: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[RDD 20373: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[RDD 20373: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 20373: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20387, syscall 41, args 1 524289 0 18446744073709548165 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[Utility AudioDecoder 20388: Main Thread]: D/Dmabuf Using DRM device /dev/dri/card0
[Utility AudioDecoder 20388: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/card0 error Permission denied
[Utility AudioDecoder 20388: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[Utility AudioDecoder 20388: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20403, syscall 41, args 1 524289 0 140177681395495 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[2022-06-26T18:51:26Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:51:26Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:51:26Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-26T18:51:26Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20420, syscall 41, args 1 524289 0 140177708777255 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20426, syscall 41, args 1 524289 0 140177681395495 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20433, syscall 41, args 1 524289 0 140177708777255 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20433, syscall 41, args 1 524289 0 140177708777255 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
[RDD 20373: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
libva info: VA-API version 1.10.0
Sandbox: seccomp sandbox violation: pid 20373, tid 20438, syscall 41, args 1 524289 0 140177681395495 20 1.
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1

(In reply to Robert Mader [:rmader] from comment #10)

Hehe, alright, the issue most likely is a totally different one: FEATURE_FAILURE_DDX_INTEL. The Intel DDX/Xorg driver is so broken that we disable Webrender altogether. Once you uninstall it and switch to the modesetting driver, things should start to just work.

Maybe this driver is totally broken, but VLC works perfectly and google-chrome to. Only firefox can't deal properly with this driver. I think this is strange. But I'll try modesetting driver later and I hope it will help.

VLC log while playing mp4 video:

$ vlc sample-5s.mp4  
VLC media player 3.0.17.4 Vetinari (revision 3.0.13-8-g41878ff4f2)
[000055b2e5c9c5b0] main libvlc: Запуск vlc с интерфейсом по умолчанию. Используйте 'cvlc' для запуска vlc без интерфейса.
[00007efe84003f10] gl gl: Initialized libplacebo v2.72.0 (API v72)
libva info: VA-API version 1.10.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[00007efe98c17520] avcodec decoder: Using Intel i965 driver for Intel(R) Kaby Lake - 2.4.1 for hardware decoding

(In reply to Robert Mader [:rmader] from comment #10)

Hehe, alright, the issue most likely is a totally different one: FEATURE_FAILURE_DDX_INTEL. The Intel DDX/Xorg driver is so broken that we disable Webrender altogether. Once you uninstall it and switch to the modesetting driver, things should start to just work.

Hehe, alright, I've tried modesetting driver on different machine with newer graphics card (Intel Gen10 CPU) and on firefox 102b9 result is exactly the same. Moreover, I've got same error messages regarding to the DRM device:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Parent 806966: Main Thread]: D/Dmabuf We're missing DRM render device!
[Child 807187: Main Thread]: D/Dmabuf We're missing DRM render device!
[Child 807187: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[Child 807187: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 0
[RDD 807314: Main Thread]: D/Dmabuf We're missing DRM render device!
[RDD 807314: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[2022-06-27T06:22:49Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-27T06:22:49Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-27T06:22:49Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[2022-06-27T06:22:49Z ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[Utility AudioDecoder 807368: Main Thread]: D/Dmabuf We're missing DRM render device!
[Utility AudioDecoder 807368: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[Utility AudioDecoder 807368: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 0 XRE_IsRDDProcess 0
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 807314: MediaSupervisor #1]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 0 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
``
And if I provide firefox with MOZ_DRM_DEVICE and MOZ_X11_EGL I get "Permission denied" message while trying to open both /dev/dri/card0 and /dev/dri/renderD128 devices. So I think that VAAPI in firefox is broken, cause there is no FEATURE_FAILURE_DDX_INTEL in the attached about:support data, following after this comment.
OS: Unspecified → Linux

X11 EGL
Blocklisted by gfxInfo

VA-API video decoding
Requires EGL

I am not an expert, but try running with MOZ_X11_EGL=1 ./firefox ?

Mesa 20.3.5

And update your driver.

(In reply to Tom Schuster [:evilpie] from comment #15)

X11 EGL
Blocklisted by gfxInfo

VA-API video decoding
Requires EGL

I am not an expert, but try running with MOZ_X11_EGL=1 ./firefox ?

I've tried to run MOZ_X11_EGL=1 MOZ_DRM_DEVICE=/dev/dri/card0 and MOZ_X11_EGL=1 MOZ_DRM_DEVICE=/dev/dri/renderD128 - no success. I've got "Permission denied" error for DRM devices.

Mesa 20.3.5

And update your driver.

I'm using Debian stable and this is the latest available version of Mesa. I think that firefox should properly work with it.

Hardware: Unspecified → x86_64

Thanks, comment 14 looks already much better. Can you repost the about:support with just MOZ_X11_EGL=1 (or gfx.x11-egl.force-enabled:true)? I don't see anything unusual so far.

(In reply to Robert Mader [:rmader] from comment #17)

Thanks, comment 14 looks already much better. Can you repost the about:support with just MOZ_X11_EGL=1 (or gfx.x11-egl.force-enabled:true)? I don't see anything unusual so far.

May be firefox restart helped, but it seems that VAAPI begins to work with MOZ_X11_EGL=1 without MOZ_DRM_DEVICE=...:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Parent 830180: Main Thread]: D/Dmabuf Using DRM device /dev/dri/renderD128
[Parent 830180: Main Thread]: D/Dmabuf nsDMABufDevice::Configure()
[Parent 830180: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 830180: Main Thread]: D/Dmabuf DMABuf is enabled
[Parent 830180: Main Thread]: D/Dmabuf VAAPIGetAcceleratedProfiles()
libva info: VA-API version 1.10.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
[Parent 830180: Main Thread]: D/Dmabuf   Initialised VAAPI connection: version 1.10
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile H264Main:
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile H264High:
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile H264ConstrainedBaseline:
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile VP8Version0_3:
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile VP9Profile0:
[Parent 830180: Main Thread]: D/Dmabuf   Supported profile VP9Profile2:
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

May be firefox restart helped, but it seems that VAAPI begins to work with MOZ_X11_EGL=1 without MOZ_DRM_DEVICE=...:

\o/
Yes, that can be - sometimes FF needs two restarts to flush some blocklists, quite annoying. Great, so IIUC this issue was about the DDX driver (blocklisting WR) and "old" Mesa (not enabled for EGL by default) and can be closed?

I'll try modesetting driver on my laptop (the initial test PC) later in the evening and then provide more information. Firefox 102b9 with MOZ_X11_EGL=1 and modesetting driver definitely works for Intel Gen10 GPU on my working PC.

I switched my laptop Xorg configuration to modesetting driver:

$ sudo grep -i kms /var/log/Xorg.0.log
[    10.362] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    11.115] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.

When I start firefox 102b9 I've got We're missing DRM render device! error message again:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Parent 5128: Main Thread]: D/Dmabuf We're missing DRM render device!
[Parent 5128: Main Thread]: D/Dmabuf nsDMABufDevice::Configure()
[Parent 5128: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
[Parent 5128: Main Thread]: D/Dmabuf Failed to create drm render device
[Parent 5128: Main Thread]: D/Dmabuf VAAPIGetAcceleratedProfiles()
[Parent 5128: Main Thread]: D/Dmabuf   Failed to get vaGetDisplayDRM()
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

But if I start firefox with $ MOZ_LOG="Dmabuf:5" MOZ_DRM_DEVICE=/dev/dri/renderD128 ./firefox about:support shows me DMABUF available by default and VAAPI accelerated decoding begins to work. intel_gpu_top shows Video graph bar load greater than zero percent.

So, it works, but only with MOZ_DRM_DEVICE pointing to the DRI device.

It's strange for me, but there are Permission denied error records in log:

[RDD 9423: Main Thread]: D/Dmabuf Using DRM device /dev/dri/renderD128
[RDD 9423: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 9423: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[Utility AudioDecoder 9467: Main Thread]: D/Dmabuf Using DRM device /dev/dri/renderD128
[Utility AudioDecoder 9467: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/renderD128 error Permission denied

(In reply to dednev from comment #22)

I switched my laptop Xorg configuration to modesetting driver:

$ sudo grep -i kms /var/log/Xorg.0.log
[    10.362] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    11.115] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.

When I start firefox 102b9 I've got We're missing DRM render device! error message again:

$ MOZ_LOG="Dmabuf:5" ./firefox
[Parent 5128: Main Thread]: D/Dmabuf We're missing DRM render device!
[Parent 5128: Main Thread]: D/Dmabuf nsDMABufDevice::Configure()
[Parent 5128: Main Thread]: D/Dmabuf Loading DMABuf system library libgbm.so.1 ...
[Parent 5128: Main Thread]: D/Dmabuf Failed to create drm render device
[Parent 5128: Main Thread]: D/Dmabuf VAAPIGetAcceleratedProfiles()
[Parent 5128: Main Thread]: D/Dmabuf   Failed to get vaGetDisplayDRM()
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

But if I start firefox with $ MOZ_LOG="Dmabuf:5" MOZ_DRM_DEVICE=/dev/dri/renderD128 ./firefox about:support shows me DMABUF available by default and VAAPI accelerated decoding begins to work. intel_gpu_top shows Video graph bar load greater than zero percent.

So, it works, but only with MOZ_DRM_DEVICE pointing to the DRI device.

Strange - are you sure that you don't have something like MOZ_DRM_DEVICE= set globally or so? Even if not, this should go away once you update to a Mesa version that supports EXT_device_drm_render_node.

It's strange for me, but there are Permission denied error records in log:

[RDD 9423: Main Thread]: D/Dmabuf Using DRM device /dev/dri/renderD128
[RDD 9423: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[RDD 9423: Main Thread]: D/Dmabuf nsDMABufDevice::IsDMABufVAAPIEnabled: EGL 1 media_ffmpeg_vaapi_enabled 1 CanUseHardwareVideoDecoding 1 XRE_IsRDDProcess 1
[Utility AudioDecoder 9467: Main Thread]: D/Dmabuf Using DRM device /dev/dri/renderD128
[Utility AudioDecoder 9467: Main Thread]: D/Dmabuf Failed to open drm render node /dev/dri/renderD128 error Permission denied

Note that the warning does not occur in the RDD process, which is the one that matters for VA-API. So this likely only affects processes that shouldn't need to open it anyway (and we should try to silence it at some point).

(In reply to Robert Mader [:rmader] from comment #23)

(In reply to dednev from comment #22)
Strange - are you sure that you don't have something like MOZ_DRM_DEVICE= set globally or so?

Yes, I'm totally sure:

$ env |grep MOZ
MOZ_X11_EGL=1
$

Even if not, this should go away once you update to a Mesa version that supports EXT_device_drm_render_node.

I hope so, but I can't check this case at this moment cause I have no with to update my stable Debian to testing.

Note that the warning does not occur in the RDD process, which is the one that matters for VA-API. So this likely only affects processes that shouldn't need to open it anyway (and we should try to silence it at some point).

Yes, by however I can't understand what process tries to open it and fails. I suppose that this is bug, but not so serious as failed VAAPI hardware decoding.

Can you provide your about:support once more, with MOZ_X11_EGL=1 but without MOZ_DRM_DEVICE=/dev/dri/renderD128?

So IIUC there's a secondary Nvidia GPU present in the setup. This previously caused problems in a bunch of cases, especially if the proprietary nvidia driver was installed or not properly uninstalled.

You could try disabling that GPU in the bios - otherwise you'll likely need to wait for mesa/nvidia-driver/libglvnd updates.

(In reply to Robert Mader [:rmader] from comment #27)

So IIUC there's a secondary Nvidia GPU present in the setup. This previously caused problems in a bunch of cases, especially if the proprietary nvidia driver was installed or not properly uninstalled.

It seems you're right, after uninstalling Nvidia proprietary driver package through $ sudo /usr/bin/nvidia-uninstall I could start firefox with proper DRM device detection if only MOZ_X11_EGL=1 is set (no other MOZ_* environment variables).

You could try disabling that GPU in the bios - otherwise you'll likely need to wait for mesa/nvidia-driver/libglvnd updates.

Nvidia driver uninstall is enough for me. I'm waiting for Firefox 102 to be released. Thank you for your efforts, my problem is solved.

(In reply to Max A. Dednev from comment #28)

You could try disabling that GPU in the bios - otherwise you'll likely need to wait for mesa/nvidia-driver/libglvnd updates.

Nvidia driver uninstall is enough for me. I'm waiting for Firefox 102 to be released. Thank you for your efforts, my problem is solved.

Great, thanks for the feedback. As said above this issues should go away in the future, IIRC it might have been fixed by some libglvnd update.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

Hello,
There was suggestion to uninstall nVidia proprietary driver for discrete adapter in my laptop to get Intel video decoding working. And it helps, but I need nVidia proprietary driver for some application graphic rendering offloading. So I've found a way to get Intel video decoding working with nVidia proprietary drivers installed. The root of my problems was MESA driver loader, which tries to load /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so for nVidia card, having already loaded proprietary driver. And after I've renamed /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so driver to /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.s0 to prevent it from being loaded Intel GPU video decoding begin to work again. I hope this help others to get Intel VAAPI working with Firefox.

But there is one fact, that I can't understand: VLC works perfectly without renaming. So I thing that there is some issues in Firefox/MESA loader interaction during initialization and this breaks VAAPI decoding and produces EGL errors. I've attached new log file, got from running MOZ_LOG="Dmabuf:5" EGL_LOG_LEVEL=debug firefox >firefox-20230526.log 2>&1

Attached file firefox-20230526.log —
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Summary: Failed to use DRM device for video decoding → [X11/Intel/NVIDIA] Failed to use DRM device for video decoding when NVIDIA proprietary drivers are installed on secondary GFX card

Okay let's add it back to tracker.

Thanks, this sounds like we need to improve the error path when iterating over the device list and not bail out on error.

I've attached firefox log file with removed nouveau_dri.so library file (MESA fails to load it) and you could find, that the main difference is following message sequence:

libEGL debug: pci id for fd 29: 10de:134e, driver nouveau

libEGL debug: MESA-LOADER: dlopen(/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so)

libEGL debug: found extension `DRI_Core'
libEGL info: found extension DRI_Core version 2
libEGL debug: found extension `DRI_IMAGE_DRIVER'
libEGL info: found extension DRI_IMAGE_DRIVER version 1
libEGL debug: found extension `DRI_DRI2'
libEGL debug: found extension `DRI_ConfigOptions'
libEGL debug: found extension `DRI_Core'
libEGL debug: found extension `DRI_IMAGE_DRIVER'
libEGL debug: found extension `DRI_DRI2'
libEGL debug: found extension `DRI_ConfigOptions'
libEGL info: found extension DRI_ConfigOptions version 2
ATTENTION: default value of option mesa_glthread overridden by environment.
libEGL warning: DRI2: failed to create dri screen
libEGL debug: EGL user error 0x3001 (EGL_NOT_INITIALIZED) in eglInitialize: DRI2: failed to create screen

libEGL debug: using driver nvidia-drm for 29

libEGL debug: pci id for fd 29: 10de:134e, driver nouveau

libEGL debug: using driver i915 for 29

libEGL debug: using driver i915 for 29

libEGL debug: pci id for fd 29: 8086:5916, driver iris

libEGL debug: Falling back to surfaceless swrast without DRM.
libEGL debug: MESA-LOADER: dlopen(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so)

After nouveau_dri.so loading DRI initialization fails, and DRM falls back to swrast, and not to the iris_dri.so which supports first available video card.

Another strange behavior in log are showed by lines:

libEGL debug: using driver nvidia-drm for 29

libEGL debug: pci id for fd 29: 10de:134e, driver nouveau

nvidia-drm is installed and configured proprietary driver, but nouveau is not installed, not configured and not loaded according to the lspci -vvv output:

01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 930MX] (rev a2)
	Subsystem: Hewlett-Packard Company GM108M [GeForce 930MX]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 133
	IOMMU group: 10
	Region 0: Memory at f2000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at 4000 [size=128]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee003b8  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 25.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <512ns, L1 unlimited
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x4 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via message, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [250 v1] Latency Tolerance Reporting
		Max snoop latency: 34326183936ns
		Max no snoop latency: 34326183936ns
	Capabilities: [258 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=255us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=0ns
		L1SubCtl2: T_PwrOn=44us
	Capabilities: [128 v1] Power Budgeting <?>
	Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Capabilities: [900 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia

So I can't understand why I see here libEGL debug: pci id for fd 29: 10de:134e, driver nouveau line.

Will try to look into this soon, now that we'll ship VAAPI by default on Intel and this will affect way more users.

Flags: needinfo?(robert.mader)

Meh, had a look and apparently the error happens outside our control / is not easy to fix on our side. Not entirely sure, but I now think this is a libglvnd issue.

Flags: needinfo?(robert.mader)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: