Skip to content
Snippets Groups Projects
New look: Off

Any vulkan usage spams virtgpu / gfxstream errors

    • Open Issue created by Shmerl @shmerl

    After upgrading to Mesa 25.0.1 in Debian testing, any Vulkan usage (for example running vulkaninfo) started producing these errors:

    MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Invalid argument, continuing without context...
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument
MESA: error: Failed to create virtgpu AddressSpaceStream
MESA: error: vulkan: Failed to get host connection
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -4 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_gfxstream.so. Skipping this driver.
    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Shmerl mentioned in issue #12209 (closed)

      mentioned in issue #12209 (closed)

    • Shmerl changed the description

      changed the description

    • Sally A. haj
      Sally A. haj @sallyhaj ·

      I have the similar result in Raspberry Pi 5 with Mesa 25.0.1 in Debian Testing

      vkcube
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
Segmentation fault
      vulkaninfo
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
Segmentation fault

      I think in broadcom Raspberry Pi, should be 'v3d' not virtgpu. How to resolve the issue Thank you.

    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      This happens when vulkan loader scans all existing drivers, like in my case it will use radv, but it spams these errors when loading gfxstream.

      You can see more details on the sequence by adding VK_LOADER_DEBUG=all

    • Yiwei Zhang added gfxstream label

      added gfxstream label

    • Sally A. haj
      Sally A. haj @sallyhaj ·

      Thank you @shmerl , here the result of vkcube

      VK_LOADER_DEBUG=all vkcube
INFO:              Vulkan Loader Version 1.4.304
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
DRIVER:            Searching for driver manifest files
DRIVER:               In following locations:
DRIVER:                  /home/sally/.config/vulkan/icd.d
DRIVER:                  /etc/xdg/vulkan/icd.d
DRIVER:                  /etc/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/vulkan/icd.d
DRIVER:                  /usr/share/gnome/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /var/lib/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /usr/local/share/vulkan/icd.d
DRIVER:                  /usr/share/vulkan/icd.d
DRIVER:               Found the following files:
DRIVER:                  /usr/share/vulkan/icd.d/lvp_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/radeon_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/virtio_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/lvp_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_lvp.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_broadcom.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_freedreno.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_nouveau.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_panfrost.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_radeon.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/virtio_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_virtio.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_gfxstream.so
DRIVER:            Searching for driver manifest files
DRIVER:               In following locations:
DRIVER:                  /home/sally/.config/vulkan/icd.d
DRIVER:                  /etc/xdg/vulkan/icd.d
DRIVER:                  /etc/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/vulkan/icd.d
DRIVER:                  /usr/share/gnome/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /var/lib/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /usr/local/share/vulkan/icd.d
DRIVER:                  /usr/share/vulkan/icd.d
DRIVER:               Found the following files:
DRIVER:                  /usr/share/vulkan/icd.d/lvp_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/radeon_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/virtio_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/lvp_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_lvp.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_broadcom.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_freedreno.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_nouveau.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_panfrost.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_radeon.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/virtio_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_virtio.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_gfxstream.so
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
Segmentation fault

      And Here the result of vulkaninfo

      VK_LOADER_DEBUG=all vulkaninfo
INFO:              Vulkan Loader Version 1.4.304
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for explicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/explicit_layer.d
LAYER:                   /etc/xdg/vulkan/explicit_layer.d
LAYER:                   /etc/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /usr/local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/vulkan/explicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version 1.2.0)
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json (file version 1.0.0)
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for explicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/explicit_layer.d
LAYER:                   /etc/xdg/vulkan/explicit_layer.d
LAYER:                   /etc/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /usr/local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/vulkan/explicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version 1.2.0)
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json (file version 1.0.0)
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for explicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/explicit_layer.d
LAYER:                   /etc/xdg/vulkan/explicit_layer.d
LAYER:                   /etc/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /usr/local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/vulkan/explicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version 1.2.0)
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json (file version 1.0.0)
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
LAYER:             Searching for explicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/explicit_layer.d
LAYER:                   /etc/xdg/vulkan/explicit_layer.d
LAYER:                   /etc/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/explicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/explicit_layer.d
LAYER:                   /usr/local/share/vulkan/explicit_layer.d
LAYER:                   /usr/share/vulkan/explicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json
LAYER:                   /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version 1.2.0)
INFO:              Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json (file version 1.0.0)
INFO:              No valid vk_loader_settings.json file found, no loader settings will be active
LAYER:             Searching for implicit layer manifest files
LAYER:                In following locations:
LAYER:                   /home/sally/.config/vulkan/implicit_layer.d
LAYER:                   /etc/xdg/vulkan/implicit_layer.d
LAYER:                   /etc/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/gnome/vulkan/implicit_layer.d
LAYER:                   /home/sally/.local/share/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /var/lib/flatpak/exports/share/vulkan/implicit_layer.d
LAYER:                   /usr/local/share/vulkan/implicit_layer.d
LAYER:                   /usr/share/vulkan/implicit_layer.d
LAYER:                Found the following files:
LAYER:                   /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
INFO:              Found manifest file /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json (file version 1.0.0)
DRIVER:            Searching for driver manifest files
DRIVER:               In following locations:
DRIVER:                  /home/sally/.config/vulkan/icd.d
DRIVER:                  /etc/xdg/vulkan/icd.d
DRIVER:                  /etc/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/vulkan/icd.d
DRIVER:                  /usr/share/gnome/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /var/lib/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /usr/local/share/vulkan/icd.d
DRIVER:                  /usr/share/vulkan/icd.d
DRIVER:               Found the following files:
DRIVER:                  /usr/share/vulkan/icd.d/lvp_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/radeon_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/virtio_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/lvp_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_lvp.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_broadcom.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_freedreno.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_nouveau.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_panfrost.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_radeon.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/virtio_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_virtio.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_gfxstream.so
DRIVER:            Searching for driver manifest files
DRIVER:               In following locations:
DRIVER:                  /home/sally/.config/vulkan/icd.d
DRIVER:                  /etc/xdg/vulkan/icd.d
DRIVER:                  /etc/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/vulkan/icd.d
DRIVER:                  /usr/share/gnome/vulkan/icd.d
DRIVER:                  /home/sally/.local/share/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /var/lib/flatpak/exports/share/vulkan/icd.d
DRIVER:                  /usr/local/share/vulkan/icd.d
DRIVER:                  /usr/share/vulkan/icd.d
DRIVER:               Found the following files:
DRIVER:                  /usr/share/vulkan/icd.d/lvp_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/radeon_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/virtio_icd.aarch64.json
DRIVER:                  /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/lvp_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_lvp.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/broadcom_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_broadcom.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/freedreno_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_freedreno.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/nouveau_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_nouveau.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/panfrost_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_panfrost.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_radeon.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/virtio_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_virtio.so
DRIVER:            Found ICD manifest file /usr/share/vulkan/icd.d/gfxstream_vk_icd.aarch64.json, version 1.0.0
DEBUG | DRIVER:    Searching for ICD drivers named /usr/lib/aarch64-linux-gnu/libvulkan_gfxstream.so
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      segmentation fault is really wrong, in my case it just spams errors but they are cosmetic and in the end the loader picks radv properly.

    • Simon Richter
      Simon Richter @GyrosGeier ·

      It seems the virtgpu driver doesn't check the name of the kernel module behind the render node and starts blindly submitting ioctls. This never fails, because new always returns an object or throws.

    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      Looks like at least some of the messages will be skipped thanks to this:

      9447de5d

    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      cc @gurchetansingh

    • Gurchetan Singh mentioned in merge request !34090 (merged)

      mentioned in merge request !34090 (merged)

    • Gurchetan Singh
      Gurchetan Singh @gurchetansingh ·
      Developer

      Thank you for the bug report! Please test/review !34090 (merged) for proposed fix.

    • Shmerl changed title from Any vulkan usage spams virtgpu / gfxtream errors to Any vulkan usage spams virtgpu / gfxstream errors

      changed title from Any vulkan usage spams virtgpu / gfxtream errors to Any vulkan usage spams virtgpu / gfxstream errors

    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      Can't easily apply it on top of 25.0.1, but I managed to modify the MR to test it and it helps, thank you!

      Here are my resulting patches for 25.0.1 if anyone wants to test (not 100% clean but they apply):

      Can you please backport your fixes 25.0.x too so next bugfix release will include this?

      Edited by Shmerl
    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      Btw, your fix was missing to suppress these messages (so I had to add some of that, see the third patch file).

      If anyone can test the MR with Mesa main it would be useful too.

      Edited by Shmerl
    • Sally A. haj
      Sally A. haj @sallyhaj ·

      I think I did that, from here mesa on  mesa-gfxstream-distro-vk-loader-fixes, I have done these:

      meson setup builddir/
meson compile -C builddir/
sudo meson install -C builddir/

      After rebooting the system, I got the same results with vkcube

       vkcube
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_3D_FEATURES
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CAPSET_QUERY_FIX
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_RESOURCE_BLOB
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_HOST_VISIBLE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CROSS_DEVICE
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CONTEXT_INIT
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_SUPPORTED_CAPSET_IDs
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_EXPLICIT_DEBUG_NAME
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_FENCE_PASSING
MESA: info: virtgpu backend not enabling VIRTGPU_PARAM_CREATE_GUEST_HANDLE
MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument
Segmentation fault

      Note, I use Debian Trixie/testing on Raspberry Pi5 I should to mention that, in Raspberry Pi5, there is another issue #12641 which I don't know if it interfere with this or not.

      Edited by Sally A. haj
    • Gurchetan Singh
      Gurchetan Singh @gurchetansingh ·
      Developer

      https://gitlab.freedesktop.org/gurchetansingh/mesa/-/commits/25.0.1-gfxstream-distro-loader-fix <-- branch with 25.0.1 fixes. We can follow the proper process of backporting after !34090 (merged) lands.

    • Timo Aaltonen
      Timo Aaltonen @tjaalton ·
      Developer

      thanks for the patches, it's much better now but I'm still seeing this:

      WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -4 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_gfxstream.so. Skipping this driver.

      Would this be more for vulkan-loader then? That seems more suited for debugging output.

    • Shmerl
      Shmerl @shmerl ·
      Author Contributor

      I think it means gfxtream reports some error that loader doesn't expect, so it probably still needs a fix on gfxstream side. Loader scans a bunch of other stuff that's not loaded in the end, but it doesn't create warnings like that.

      Edited by Shmerl
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    Please register or sign in to reply