[Mesa-dev] [Bug 105068] vulkaninfo gives an VK_ERROR_INITIALIZATION_FAILED

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 13 03:38:52 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=105068

            Bug ID: 105068
           Summary: vulkaninfo gives an VK_ERROR_INITIALIZATION_FAILED
           Product: Mesa
           Version: 17.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Vulkan/radeon
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: ppesci at gmail.com
        QA Contact: mesa-dev at lists.freedesktop.org

On Fedora 27, with mesa-vulkan-drivers-17.2.4-3.fc27.x86_64 installed, the
output in vulkaninfo is:

===========
VULKAN INFO
===========

Vulkan API Version: 1.0.65

WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_object_tracker.json - The file has
already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_core_validation.json - The file has
already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_threading.json - The file has
already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_standard_validation.json - The file
has already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_parameter_validation.json - The file
has already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/explicit_layer.d/VkLayer_unique_objects.json - The file has
already been read once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json - The file has already been read
once
WARNING: [loader] Code 0 : Skipping manifest file
/usr/share/vulkan/icd.d/intel_icd.x86_64.json - The file has already been read
once

Instance Extensions:
====================
Instance Extensions     count = 9
        VK_KHR_surface                      : extension revision 25
        VK_KHR_xcb_surface                  : extension revision  6
        VK_KHR_xlib_surface                 : extension revision  6
        VK_KHR_wayland_surface              : extension revision  6
        VK_KHR_get_physical_device_properties2: extension revision  1
        VK_KHR_external_memory_capabilities : extension revision  1
        VK_KHR_external_semaphore_capabilities: extension revision  1
        VK_KHR_get_surface_capabilities2    : extension revision  1
        VK_EXT_debug_report                 : extension revision  9
/builddir/build/BUILD/Vulkan-LoaderAndValidationLayers-sdk-1.0.65.2/demos/vulkaninfo.c:1670:
failed with VK_ERROR_INITIALIZATION_FAILED

using;
export VK_LOADER_DEBUG=all

gives a very long output where the interesting part at the end is:

ERROR: setupLoaderTermPhysDevs:  Failed to detect any valid GPUs in the current
config
ERROR: setupLoaderTrampPhysDevs:  Failed during dispatch call of
'vkEnumeratePhysicalDevices' to lower layers or loader to get count.
/builddir/build/BUILD/Vulkan-LoaderAndValidationLayers-sdk-1.0.65.2/demos/vulkaninfo.c:1670:
failed with VK_ERROR_INITIALIZATION_FAILED

My video card is an R7 260X and is supposed to work.

lspci output;
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX
[Radeon R7 260X/360]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180213/efa168f8/attachment.html>


More information about the mesa-dev mailing list