gpuzelenograd / memtest_vulkan Goto Github PK
View Code? Open in Web Editor NEWVulkan compute tool for testing video memory stability
Home Page: https://github.com/GpuZelenograd/memtest_vulkan/blob/main/Readme.md
License: zlib License
memtest_vulkan's People
Stargazers
Watchers
memtest_vulkan's Issues
radv/amdgpu: Failed to allocate a buffer
I have a RX 7900 XTX, and it looks like not all of my memory is being tested. When I launch normally, I see:
1: Bus=0x09:00 DevId=0x744C 24GB AMD Radeon RX 7900 XTX (RADV GFX1100)
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 23927123968 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 23507693568 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 23088263168 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 22668832768 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 22249402368 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 21829971968 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 21410541568 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 20991111168 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 20571680768 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 20152250368 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 19732819968 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 19313389568 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 18893959168 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 18474528768 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 18055098368 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 17635667968 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 17216237568 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
radv/amdgpu: Failed to allocate a buffer:
radv/amdgpu: size : 16796807168 bytes
radv/amdgpu: alignment : 262144 bytes
radv/amdgpu: domains : 4
Standard 5-minute test of 1: Bus=0x09:00 DevId=0x744C 24GB AMD Radeon RX 7900 XTX (RADV GFX1100)
1 iteration. Passed 0.0310 seconds written: 11.2GB 864.3GB/sec checked: 15.0GB 832.2GB/sec
I have resizable BAR turned on in my bios.
I will attach the output I see running with the file renamed to memtest_vulkan_verbose.
It also appears that the tool crashes if I write to a log file with tee using a pipe. (i.e. ./memtest_vulkan_verbose | tee memtest_vulkan_verbose.txt will crash when ctrl+c is pressed)
memtest_vulkan_verbose.txt
Nvidia 1GB Quadro K600 (Video-Card) - INIT OR FIRST testing failed due to runtime error
Hi, starting memtest_vulcan_verbose results in the following:
./memtest_vulkan_verbose
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.275
Available:
VK_LAYER_NV_optimus, VK_LAYER_MESA_device_select
Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_acquire_drm_display, VK_EXT_surface_maintenance1, VK_EXT_swapchain_colorspace, VK_KHR_portability_enumeration, VK_LUNARG_direct_driver_loading
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
1: Bus=0x01:00 DevId=0x0FFA API 1.2.175 v470(0x75BBC180) 1GB Quadro K600
2: Bus=0x00:00 DevId=0x0000 API 1.3.267 ver1 8GB llvmpipe (LLVM 17.0.6, 128 bits)
Override index to test:1
Loading memory info for selected device index 0...
heap size 1.0GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL
heap size 5.6GB budget 5.6GB usage 0.0GB flags=(empty)
Spawned child Child { stdin: None, stdout: None, stderr: None, .. } with PID 13864
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.275
Available:
VK_LAYER_NV_optimus, VK_LAYER_MESA_device_select
Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_acquire_drm_display, VK_EXT_surface_maintenance1, VK_EXT_swapchain_colorspace, VK_KHR_portability_enumeration, VK_LUNARG_direct_driver_loading
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
Loading memory info for selected device index 0...
heap size 1.0GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL
heap size 5.6GB budget 5.6GB usage 0.0GB flags=(empty)
Runtime error: Failed determining memory budget
Subprocess status exit status: 68 parent_close_requested false
Using in-process testing method with small memory limit 0
Using in-process testing method
Runtime error: Failed determining memory budget
memtest_vulkan: INIT OR FIRST testing failed due to runtime error
press any key to continue...
What are your thoughts on this?
-Thanks
Drastically different bandwidth to the expected with default memory usage (pair of 4k HDR displays)
So, I noticed you used a RTX 2070 to take those screenshots, which uses a memory subsystem with identical specs to my RTX 3060 Ti, but I'm getting 32 to 43GB/s, while the screenshots show 317 to 327GB/s and noticed on HWInfo that I had 100% core usage, even though it's a more powerful GPU than the 2070.
Low-memory iGPU reports "Failed determining memory budget"
I have quite a similar error message but different system (using iGPU)
GPU: Vega 3 iGPU (R3 3200U)
UMA: 512M
RAM: 16GB
OS: Windows 11 Latest Insider Beta
bagusnl_reg ~ memtest_vulkan_verbose.exe in cmd at 15:16:25 https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd To finish testing use Ctrl+C WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.261 WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files. WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files. Available: VK_LAYER_AMD_switchable_graphics, VK_LAYER_VALVE_steam_overlay, VK_LAYER_VALVE_steam_fossilize, VK_LAYER_RTSS WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer Extensions: VK_KHR_device_group_creation, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_win32_surface, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_swapchain_colorspace, VK_KHR_portability_enumeration, VK_LUNARG_direct_driver_loadingWARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.1: Bus=0x03:00 DevId=0x15D8 API 1.3.262 0x80011B 1GB AMD Radeon(TM) Vega 3 Graphics
2: Bus=0x03:00 DevId=0x15D8 API 1.3.262 0x80011B 1GB AMD Radeon(TM) Vega 3 Graphics
Override index to test:1
Loading memory info for selected device index 0...
heap size 0.2GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL | MULTI_INSTANCE | MULTI_INSTANCE_KHR
heap size 7.5GB budget 7.1GB usage 0.0GB flags=(empty)
heap size 0.2GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL | MULTI_INSTANCE | MULTI_INSTANCE_KHR
Spawned child Child { stdin: None, stdout: None, stderr: None, .. } with PID 34076
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.261
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
Available:
VK_LAYER_AMD_switchable_graphics, VK_LAYER_VALVE_steam_overlay, VK_LAYER_VALVE_steam_fossilize, VK_LAYER_RTSS
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
Extensions: VK_KHR_device_group_creation, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_win32_surface, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_swapchain_colorspace, VK_KHR_portability_enumeration, VK_LUNARG_direct_driver_loadingWARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
WARNING: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
WARNING | LAYER: windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
Loading memory info for selected device index 0...
heap size 0.2GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL | MULTI_INSTANCE | MULTI_INSTANCE_KHR
heap size 7.5GB budget 7.1GB usage 0.0GB flags=(empty)
heap size 0.2GB budget 0.2GB usage 0.0GB flags=DEVICE_LOCAL | MULTI_INSTANCE | MULTI_INSTANCE_KHR
Runtime error: Failed determining memory budget
Subprocess status exit code: 68 parent_close_requested false
Using in-process testing method with small memory limit 0
Using in-process testing method
Runtime error: Failed determining memory budgetmemtest_vulkan: INIT OR FIRST testing failed due to runtime error
press any key to continue...
vulkaninfo output: https://gist.github.com/bagusnl/eb2125cf9e7c606b62c7dedd659b2753
Originally posted by @bagusnl in #11 (comment)
fails to initialise on MoltenVK: `VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR`
DRIVER: Searching for driver manifest files
DRIVER: In following locations:
DRIVER: /nix/store/gi6ylcisphlks0avxsz7w67bny12h4j5-MoltenVK-1.2.7/share/vulkan/icd.d/MoltenVK_icd.json
DRIVER: Found the following files:
DRIVER: /nix/store/gi6ylcisphlks0avxsz7w67bny12h4j5-MoltenVK-1.2.7/share/vulkan/icd.d/MoltenVK_icd.json
DRIVER: Found ICD manifest file /nix/store/gi6ylcisphlks0avxsz7w67bny12h4j5-MoltenVK-1.2.7/share/vulkan/icd.d/MoltenVK_icd.json, version 1.0.0
DEBUG | DRIVER: Searching for ICD drivers named /nix/store/gi6ylcisphlks0avxsz7w67bny12h4j5-MoltenVK-1.2.7/lib/libMoltenVK.dylib
ERROR | DRIVER: vkCreateInstance: Found drivers that contain devices which support the portability subset, but the instance does not enumerate portability drivers! Applications that wish to enumerate portability drivers must set the VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR bit in the VkInstanceCreateInfo flags and enable the VK_KHR_portability_enumeration instance extension.
ERROR | DRIVER: vkCreateInstance: Found no drivers!
memtest_vulkan: early exit during init: ERROR_INCOMPATIBLE_DRIVER while getting erupt::generated::InstanceLoader in context instance. Try specifying icd.json via VK_DRIVER_FILES env var
press any key to continue...
AMD GPU wants "deviceCoherentMemory" to be enabled
I tested release v0.4.0 on Archlinux. It seems to work fine but when I start it the following validation error will get printed:
Validation Error: [ VUID-vkAllocateMemory-deviceCoherentMemory-02790 ] Object 0: handle = 0x56198c13d100, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x8830dc95 | vkAllocateMemory: attempting to allocate memory type 5, which includes the VK_MEMORY_PROPERTY_DEVICE_COHERENT_BIT_AMD memory property, but the deviceCoherentMemory feature is not enabled. The Vulkan spec states: If the deviceCoherentMemory feature is not enabled, pAllocateInfo->memoryTypeIndex must not identify a memory type supporting VK_MEMORY_PROPERTY_DEVICE_COHERENT_BIT_AMD (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkAllocateMemory-deviceCoherentMemory-02790)
I use an RX 5700 as GPU with the RADV Vulkan drivers from the Mesa project. It seems to be an AMD related issue because it states that you will need to enable a feature from an AMD specific extension (VK_AMD_device_coherent_memory) to use the device coherent memory. Otherwise I don't get any validation errors.
Hope this helps!
How do you change memory block size?
I want to change it from 1.8GB to 4GB to 8GB to 16GB ...etc to see if it corrupts memory
rtx 3060 gets checkered screen freeze after short time
log output nothing unusual:
Tester console logging started at 2023-12-06T19:26:41.868859Z
1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
2: Bus=0x00:00 DevId=0x0000 2GB llvmpipe (LLVM 12.0.0, 256 bits)
Tester worker logging started at 2023-12-06T19:26:47.192084Z
Standard 5-minute test of 1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
1 iteration. Passed 0.0592 seconds written: 7.2GB 311.8GB/sec checked: 10.9GB 302.8GB/sec
18 iteration. Passed 1.0195 seconds written: 123.2GB 306.1GB/sec checked: 184.9GB 299.7GB/sec
101 iteration. Passed 5.0456 seconds written: 601.8GB 301.9GB/sec checked: 902.6GB 295.7GB/sec
598 iteration. Passed 30.0469 seconds written: 3603.2GB 303.1GB/sec checked: 5404.9GB 297.7GB/sec
1094 iteration. Passed 30.0452 seconds written: 3596.0GB 302.9GB/sec checked: 5394.0GB 296.8GB/sec
Tester console logging started at 2023-12-06T19:44:45.371219Z
1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
2: Bus=0x00:00 DevId=0x0000 2GB llvmpipe (LLVM 12.0.0, 256 bits)
Tester worker logging started at 2023-12-06T19:44:48.721239Z
Standard 5-minute test of 1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
1 iteration. Passed 0.0573 seconds written: 7.2GB 314.5GB/sec checked: 10.9GB 318.0GB/sec
18 iteration. Passed 1.0042 seconds written: 123.2GB 304.9GB/sec checked: 184.9GB 308.1GB/sec
102 iteration. Passed 5.0157 seconds written: 609.0GB 301.6GB/sec checked: 913.5GB 304.9GB/sec
605 iteration. Passed 30.0524 seconds written: 3646.8GB 301.5GB/sec checked: 5470.1GB 304.6GB/sec
1107 iteration. Passed 30.0507 seconds written: 3639.5GB 300.9GB/sec checked: 5459.2GB 304.0GB/sec
Tester console logging started at 2023-12-06T21:21:09.267532Z
1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
2: Bus=0x00:00 DevId=0x0000 2GB llvmpipe (LLVM 12.0.0, 256 bits)
Tester worker logging started at 2023-12-06T21:21:15.257429Z
Standard 5-minute test of 1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
1 iteration. Passed 0.0577 seconds written: 7.2GB 314.7GB/sec checked: 10.9GB 313.9GB/sec
19 iteration. Passed 1.0367 seconds written: 130.5GB 314.4GB/sec checked: 195.8GB 314.9GB/sec
104 iteration. Passed 5.0253 seconds written: 616.2GB 306.4GB/sec checked: 924.4GB 306.7GB/sec
Tester console logging started at 2023-12-07T00:41:09.628432Z
1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
2: Bus=0x00:00 DevId=0x0000 2GB llvmpipe (LLVM 12.0.0, 256 bits)
Tester worker logging started at 2023-12-07T00:41:13.233889Z
Standard 5-minute test of 1: Bus=0x07:00 DevId=0x2504 12GB NVIDIA GeForce RTX 3060
1 iteration. Passed 0.0553 seconds written: 7.0GB 315.1GB/sec checked: 10.5GB 317.0GB/sec
19 iteration. Passed 1.0207 seconds written: 126.0GB 307.0GB/sec checked: 189.0GB 309.7GB/sec
107 iteration. Passed 5.0279 seconds written: 616.0GB 304.6GB/sec checked: 924.0GB 307.4GB/sec
630 iteration. Passed 30.0137 seconds written: 3661.0GB 302.7GB/sec checked: 5491.5GB 306.4GB/secI must reboot to restore function. Mostly this card is working fine, but using this test, and under random occasion with heavy load getting this problem, but I can't diagnose.
Can you fix the Vulkan usage in a set of emulators?
One of the emulators in the set works for the most part (It just has black overlaying the game) while the other has an error when creating the compute pipeline. The source code for them can be found at https://sourceforge.net/projects/hpsx64/files/Source/v0410/hpsx64v0410.tar.xz/download.
Better design for multiple parallel runs
- Output device info to window title
- Prefix log output with a string containing PID
Runtime error: Failed determining memory budget
Running on Endeavor OS latest I get:
1: Bus=0x0A:00 DevId=0x2206 10GB NVIDIA GeForce RTX 3080
Runtime error: Failed determining memory budget
Using in-process testing method with small memory limit 0
Using in-process testing method
Runtime error: Failed determining memory budget
memtest_vulkan: INIT OR FIRST testing failed due to runtime error
press any key to continue...
amdgpu: GPU reset begin!
I tried the app, but the system crashed. Screen black, fans full, had to power down by long press of power button. The logs app in Ubuntu shows this in the hardware section (amdgpu:...), specifically: Message amdgpu 0000:29:00.0: amdgpu: GPU reset begin! , kernel device +pci:0000:29:00.0 , priority 6
Is my card faulty? Could it be a driver issue? Thank you
Ubuntu 22.04, AMD RX 480
Logs app also shows: 1. [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, signaled seq=610763, emitted seq=610766
2. [drm:amdgpu_job_timedout [amdgpu]] ERROR Process information: process memtest_vulkan pid 8380 thread memtest_vulkan pid 8380
Tool uses only up to 90% of vram when more is available
Can it be used for full memory range tests?
I have an assumption that my rx5700 fails on full load for some reason. Either vbios has incorrect vram size set or there is a faulty chip. Either way the amdgpu driver times out ring_gfx.
Question about results
Hi, I'm sorry if this is the wrong place to ask but I am desperate for solutions. I have recently gotten issues with games crashing/driver time out. I came across your tool and I got the following results:
Tester console logging started at 2023-10-16T23:54:13.091596Z
1: Bus=0x28:00 DevId=0x73DF 12GB AMD Radeon RX 6700 XT
Tester worker logging started at 2023-10-16T23:54:13.133822Z
Standard 5-minute test of 1: Bus=0x28:00 DevId=0x73DF 12GB AMD Radeon RX 6700 XT
1 iteration. Passed 0.0689 seconds written: 7.0GB 279.9GB/sec checked: 10.5GB 239.5GB/sec
17 iteration. Passed 1.0451 seconds written: 112.0GB 297.6GB/sec checked: 168.0GB 251.2GB/sec
94 iteration. Passed 5.0549 seconds written: 539.0GB 296.4GB/sec checked: 808.5GB 249.8GB/sec
548 iteration. Passed 30.0475 seconds written: 3178.0GB 293.3GB/sec checked: 4767.0GB 248.1GB/sec
1001 iteration. Passed 30.0407 seconds written: 3171.0GB 292.9GB/sec checked: 4756.5GB 247.6GB/sec
1454 iteration. Passed 30.0239 seconds written: 3171.0GB 293.1GB/sec checked: 4756.5GB 247.7GB/sec
1906 iteration. Passed 30.0015 seconds written: 3164.0GB 292.3GB/sec checked: 4746.0GB 247.5GB/sec
2357 iteration. Passed 30.0115 seconds written: 3157.0GB 291.4GB/sec checked: 4735.5GB 246.9GB/sec
2812 iteration. Passed 30.0526 seconds written: 3185.0GB 294.1GB/sec checked: 4777.5GB 248.5GB/sec
3264 iteration. Passed 30.0280 seconds written: 3164.0GB 291.9GB/sec checked: 4746.0GB 247.3GB/sec
3719 iteration. Passed 30.0082 seconds written: 3185.0GB 294.4GB/sec checked: 4777.5GB 249.0GB/sec
4172 iteration. Passed 30.0513 seconds written: 3171.0GB 292.4GB/sec checked: 4756.5GB 247.6GB/sec
Error found. Mode INITIAL_READ, total errors 0x14E out of 0x38000000 (0.00003555%)
Errors address range: 0xE042FECC..=0x18FF2C2CF iteration:4173
values range: 0xFEA05162..=0x0055D773 FFFFFFFF-like count:0 bit-level stats table:
0x0 0x1 0x2 0x3| 0x4 0x5 0x6 0x7| 0x8 0x9 0xA 0xB| 0xC 0xD 0xE 0xF
SinglIdx | 330| |
0x1? 2 | | |
TogglCnt 332 2 | | |
1sInValu | 1 3| 3 23 35 58| 81 49 45 22
0x1? 10 3 1 | | |
Is it likely that these VRAM errors cause games crashing? And if so, is there a way to fix this or do I have to replace the VRAM module?
Add switch to stop memtest when error was detected.
Starting header updates
- add note that it is not a benchmark and maximal throughput is not achieved
No GTT->VRAM unswapping with amdgpu + memtest_vulkan
While I was looking into some performance issues in games when VRAM is overallocated I had initially reported this issue here and used some scripting around your super useful memtest_vulkan tool (thanks again!) to benchmark. And got the response on the amd-gfx kernel mailing list that amdgpu should be able to move memory from GTT back to VRAM.
So I was wondering, is there maybe something memtest_vulkan might be doing in particular (or Vulkan in general?) that might hinder moving memory back from GTT to VRAM in my benchmark runs with memtest_vulkan? Specifically tests 5 and especially test 6 in the benchmarks I linked above seem to have an unexpectedly low performance.
(just asking in case you might have an idea - still feels more like an amdgpu issue (bug?) to me 😄 - and also mentioning it if there were maybe some features that could be interesting to add to memtest_vulkan itself that would have simplified the benchmarking script / that would have avoided those SIGSTOP'ing steps)
Tool doesn't utilize bandwith fully
Tool only reaches ~75%/80% of theoretical bandwidth on RTX 3090. Doesn't seem to be enough to stress test memory
6547 iteration. Passed 30.0083 seconds written:10766.2GB 758.7GB/sec checked:12919.5GB 816.7GB/sec
7140 iteration. Passed 30.0201 seconds written:10748.1GB 756.2GB/sec checked:12897.8GB 816.0GB/sec
7733 iteration. Passed 30.0018 seconds written:10748.1GB 756.2GB/sec checked:12897.8GB 816.9GB/sec
8327 iteration. Passed 30.0347 seconds written:10766.2GB 756.8GB/sec checked:12919.5GB 817.2GB/sec
Build does not discover and link libvulkan.so.1
In packaging this for Nixpkgs, I had to resort to patchelf'ing in a NEEDED in order to get memtest_vulkan to discover vulkan-loader.
The build script should discover the vulkan-loader on its own via the likes of pkg-config or cmake or add a mechanism to declare its path somehow.
We put the library into the LDFLAGS, PKG_CONFIG_PATH and CMAKE_PREFIX_PATH by default. We do not have a global library path at runtime (which is how I assume it manages to dlopen libvulkan.so on FHS distros?).
[Feature Request / Wishlist]: Read/write test between system RAM (or CPU cache) and VRAM
Hi,
I have an eGPU enclosure here which uses Thunderbolt 3 and it is connected to a Linux laptop with an AMD CPU + USB-C/USB4 port (40gbit/s). From the speeds I get in memtest_vulkan it seems to me that it performs read/write tests only within the GPU itself. memtest_vulkan reports 187GB/s to me, way more than the 40gbit/s the USB4 port allows.
It would be nice if memtest_vulkan had an option to measure the read/write throughput between VRAM/GPU and RAM/CPU, so that I could use it to measure the real throughput of the TB3/USB4 connection. Currently on Linux it seems a bit difficult to measure this as is (at least usbtop / usbmon don't seem to be able to capture Thunderbolt traffic).
Crash on pipe error after Ctrl+C on linux while piped to `tee`
thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', library/std/src/io/stdio.rs:1016:9
stack backtrace:
0: 0x55ba8f613d3c - <unknown>
...
13: 0x7fccf879290a - __libc_start_main
14: 0x55ba8f594e21 - <unknown>
15: 0x0 - <unknown>
failed to flush terminal: Broken pipe (os error 32)
thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', library/std/src/io/stdio.rs:1016:9
stack backtrace:
0: 0x55ba8f613d3c - <unknown>
...
14: 0x7fccf879290a - __libc_start_main
15: 0x55ba8f594e21 - <unknown>
16: 0x0 - <unknown>
thread panicked while panicking. aborting.
[sealion@pool ~]$
AMD Vega Frontier Edition 16GB HBM is reported as 24 GB
When memtest_vulkan v0.5.0 is launched, the software reports 24GB instead of 16GB.
1: Bus=0x0A:00 DevId=0x6863 24GB Radeon Vega Frontier Edition
It initially appeared to be freezing there, but it is not, it just takes a bit longer to get started with the tests.
It doesn't work on Intel Iris Xe
subject
Better handle ICD conflicts on linux
With RADV installed with lack of AMD card and presence of integrated GPU - the fake hardware is preferred over integrated GPU which is wrong:
[ ~]$ VK_LOADER_DEBUG=all ./memtest_vulkan_verbose https://github.com/GpuZelenograd/memtest_vulkan v0.5.1 by GpuZelenograd To finish testing use Ctrl+C INFO: Vulkan Loader Version 1.3.235 LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.235 LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") WARNING: vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "/usr/lib/amdvlk64.so" LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/explicit_layer.d LAYER: /etc/xdg/vulkan/explicit_layer.d LAYER: /etc/vulkan/explicit_layer.d LAYER: /home/sealion/.local/share/vulkan/explicit_layer.d LAYER: /home/sealion/.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 no files LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") WARNING: vkEnumerateInstanceLayerProperties: Unable to resolve symbol "" in implicit layer library "/usr/lib/amdvlk64.so" LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/explicit_layer.d LAYER: /etc/xdg/vulkan/explicit_layer.d LAYER: /etc/vulkan/explicit_layer.d LAYER: /home/sealion/.local/share/vulkan/explicit_layer.d LAYER: /home/sealion/.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 no files Available: VK_LAYER_NV_optimus, VK_LAYER_AMD_switchable_graphics_64 LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") DRIVER: Searching for driver manifest files DRIVER: In following folders: DRIVER: /home/sealion/.config/vulkan/icd.d DRIVER: /etc/xdg/vulkan/icd.d DRIVER: /etc/vulkan/icd.d DRIVER: /home/sealion/.local/share/vulkan/icd.d DRIVER: /home/sealion/.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/nvidia_icd.json DRIVER: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_icd.x86_64.json DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/nvidia_icd.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named libGLX_nvidia.so.0 ERROR: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0 DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_radeon.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel_hasvk.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel.so DRIVER: Searching for driver manifest files DRIVER: In following folders: DRIVER: /home/sealion/.config/vulkan/icd.d DRIVER: /etc/xdg/vulkan/icd.d DRIVER: /etc/vulkan/icd.d DRIVER: /home/sealion/.local/share/vulkan/icd.d DRIVER: /home/sealion/.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/nvidia_icd.json DRIVER: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_icd.x86_64.json DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/nvidia_icd.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named libGLX_nvidia.so.0 ERROR: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0 DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_radeon.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel_hasvk.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel.so LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") DRIVER: Searching for driver manifest files DRIVER: In following folders: DRIVER: /home/sealion/.config/vulkan/icd.d DRIVER: /etc/xdg/vulkan/icd.d DRIVER: /etc/vulkan/icd.d DRIVER: /home/sealion/.local/share/vulkan/icd.d DRIVER: /home/sealion/.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/nvidia_icd.json DRIVER: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json DRIVER: /usr/share/vulkan/icd.d/intel_icd.x86_64.json DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/nvidia_icd.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named libGLX_nvidia.so.0 ERROR: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0 DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_radeon.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel_hasvk.so DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_icd.x86_64.json, version "1.0.0" DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel.so LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /home/sealion/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d LAYER: /home/sealion/.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/nvidia_layers.json LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0") INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0") Extensions: VK_KHR_device_group_creation, VK_KHR_display, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_display_properties2, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_debug_report, VK_EXT_debug_utils, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_KHR_portability_enumerationLAYER: Searching for layer manifest files
LAYER: In following folders:
LAYER: /home/sealion/.config/vulkan/implicit_layer.d
LAYER: /etc/xdg/vulkan/implicit_layer.d
LAYER: /etc/vulkan/implicit_layer.d
LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d
LAYER: /home/sealion/.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/nvidia_layers.json
LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json
INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0")
INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0")
LAYER: Searching for layer manifest files
LAYER: In following folders:
LAYER: /home/sealion/.config/vulkan/explicit_layer.d
LAYER: /etc/xdg/vulkan/explicit_layer.d
LAYER: /etc/vulkan/explicit_layer.d
LAYER: /home/sealion/.local/share/vulkan/explicit_layer.d
LAYER: /home/sealion/.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 no files
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
LAYER: Searching for layer manifest files
LAYER: In following folders:
LAYER: /home/sealion/.config/vulkan/implicit_layer.d
LAYER: /etc/xdg/vulkan/implicit_layer.d
LAYER: /etc/vulkan/implicit_layer.d
LAYER: /home/sealion/.local/share/vulkan/implicit_layer.d
LAYER: /home/sealion/.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/nvidia_layers.json
LAYER: /usr/share/vulkan/implicit_layer.d/amd_icd64.json
INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/nvidia_layers.json (file version "1.0.0")
INFO: Found manifest file /usr/share/vulkan/implicit_layer.d/amd_icd64.json (file version "1.0.0")
LAYER: Searching for layer manifest files
LAYER: In following folders:
LAYER: /home/sealion/.config/vulkan/explicit_layer.d
LAYER: /etc/xdg/vulkan/explicit_layer.d
LAYER: /etc/vulkan/explicit_layer.d
LAYER: /home/sealion/.local/share/vulkan/explicit_layer.d
LAYER: /home/sealion/.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 no files
DRIVER: Searching for driver manifest files
DRIVER: In following folders:
DRIVER: /home/sealion/.config/vulkan/icd.d
DRIVER: /etc/xdg/vulkan/icd.d
DRIVER: /etc/vulkan/icd.d
DRIVER: /home/sealion/.local/share/vulkan/icd.d
DRIVER: /home/sealion/.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/nvidia_icd.json
DRIVER: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json
DRIVER: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json
DRIVER: /usr/share/vulkan/icd.d/intel_icd.x86_64.json
DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/nvidia_icd.json, version "1.0.0"
DEBUG | DRIVER: Searching for ICD drivers named libGLX_nvidia.so.0
ERROR: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0
DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/radeon_icd.x86_64.json, version "1.0.0"
DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_radeon.so
DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json, version "1.0.0"
DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel_hasvk.so
DRIVER: Found ICD manifest file /usr/share/vulkan/icd.d/intel_icd.x86_64.json, version "1.0.0"
DEBUG | DRIVER: Searching for ICD drivers named /usr/lib/libvulkan_intel.so
DEBUG | LAYER: Loading layer library /usr/lib/amdvlk64.so
INFO | LAYER: Insert instance layer "VK_LAYER_AMD_switchable_graphics_64" (/usr/lib/amdvlk64.so)
LAYER: vkCreateInstance layer callstack setup to:
LAYER:
LAYER: ||
LAYER:
LAYER: ||
LAYER: VK_LAYER_AMD_switchable_graphics_64
LAYER: Type: Implicit
LAYER: Disable Env Var: DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1
LAYER: Manifest: /usr/share/vulkan/implicit_layer.d/amd_icd64.json
LAYER: Library: /usr/lib/amdvlk64.so
LAYER: ||
LAYER:INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 1
INFO | DRIVER: linux_read_sorted_physical_devices:
INFO | DRIVER: Original order:
INFO | DRIVER: [0] Intel(R) HD Graphics 610 (KBL GT1)
INFO | DRIVER: [1] Null hardware (RADV NAVI10)
INFO | DRIVER: Sorted order:
INFO | DRIVER: [0] Null hardware (RADV NAVI10)
INFO | DRIVER: [1] Intel(R) HD Graphics 610 (KBL GT1)
DEBUG | DRIVER: Copying old device 0 into new device 0
DEBUG | DRIVER: Copying old device 1 into new device 11: Bus=0x00:00 DevId=0x7310 API 1.3.224 v22(0x5802003) 0GB Null hardware (RADV NAVI10)
2: Bus=0x00:02 DevId=0x5902 API 1.3.230 v22(0x5803001) 6GB Intel(R) HD Graphics 610 (KBL GT1)
After first error detected add mark of earlier found errors in each line
otherwise earlier found bugs can be hard to notice without scrolling or terminating
Correctly exit while running over ssh session
Pressing Ctrl+C while running memtest_vulkan as a single app running via a ssh session like
ssh user@host /path/to/memtest_vulkan does not lrad to immediate termination. memtets_vulkan continues heavy loading in the background.
Maybe some other signals should be handled too, need some investigation
AMD Graphics card memory recognition error
Thank you for providing this testing tool!
When I tested using the RX5600XT graphics card, I found that the tool reported 5GB of graphics memory, while my graphics card was nominally 6GB. I don't understand if this means there is a problem with my graphics card?
I used verbose mode to try to identify the problem, and the following is a screenshot:
May I ask if this indicates a problem with the graphics memory, or if your software has detected it incorrectly?
Bsod "VIDEO_MEMORY_MANAGEMENT_INTERNAL"
- plug display on intel iGPU
- plug 1050Ti cerberus without display
- boot in CSM-disabled mode
If memtest-vulkan is started while furmark is runing and utilizing 1050ti - memtest-vulkan starts fine. However if it memtest-vulkan is started while no other apps are using 1050ti - a VIDEO_MEMORY_MANAGEMENT_INTERNAL bsod happens
Issue with vulkan drivers: loader_icd_scan fails
I tried to run memtest_vulkan on Linux, both with and without root permissions. This is the result I get:
https://github.com/GpuZelenograd/memtest_vulkan v0.5.0 by GpuZelenograd
To finish testing use Ctrl+C
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.204
Available:
VK_LAYER_VALVE_steam_fossilize_32, VK_LAYER_VALVE_steam_overlay_32, VK_LAYER_VALVE_steam_fossilize_64, VK_LAYER_VALVE_steam_overlay_64, VK_LAYER_MESA_device_select, VK_LAYER_MANGOHUD_overlay, VK_LAYER_INTEL_nullhw, VK_LAYER_MESA_overlay
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
Extensions: VK_KHR_device_group_creation, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_debug_report, VK_EXT_debug_utils, VK_KHR_display, VK_KHR_get_display_properties2, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
WARNING: terminator_CreateInstance: Failed to CreateInstance in ICD 3. Skipping ICD.
1: Bus=0x03:00 DevId=0x747E API 1.3.267 v23(0x5C03002) 16GB AMD Radeon RX 7800 XT (RADV NAVI32)
2: Bus=0x12:00 DevId=0x164E API 1.3.267 v23(0x5C03002) 21GB AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)
3: Bus=0x00:00 DevId=0x0000 API 1.3.267 ver1 62GB llvmpipe (LLVM 15.0.7, 256 bits)
(first device will be autoselected in 8 seconds) Override index to test:
...testing default device confirmed
Loading memory info for selected device index 0...
heap size 31.0GB budget 30.9GB usage 0.0GB flags=(empty)
heap size 16.0GB budget 0.3GB usage 0.0GB flags=DEVICE_LOCAL
Spawned child Child { stdin: None, stdout: None, stderr: None, .. } with PID 43228
Verbose feature enabled (or 'verbose' found in name). Vulkan instance 1.3.204
Available:
VK_LAYER_VALVE_steam_fossilize_32, VK_LAYER_VALVE_steam_overlay_32, VK_LAYER_VALVE_steam_fossilize_64, VK_LAYER_VALVE_steam_overlay_64, VK_LAYER_MESA_device_select, VK_LAYER_MANGOHUD_overlay, VK_LAYER_INTEL_nullhw, VK_LAYER_MESA_overlayNING: terminator_CreateInstance: Failed to CreateInstance in ICD 3. Skipping ICD.
Load
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
Extensions: VK_KHR_device_group_creation, VK_KHR_external_fence_capabilities, VK_KHR_external_memory_capabilities, VK_KHR_external_semaphore_capabilities, VK_KHR_get_physical_device_properties2, VK_KHR_get_surface_capabilities2, VK_KHR_surface, VK_KHR_surface_protected_capabilities, VK_KHR_wayland_surface, VK_KHR_xcb_surface, VK_KHR_xlib_surface, VK_EXT_debug_report, VK_EXT_debug_utils, VK_KHR_display, VK_KHR_get_display_properties2, VK_EXT_acquire_drm_display, VK_EXT_acquire_xlib_display, VK_EXT_direct_mode_display, VK_EXT_display_surface_counter, VK_EXT_swapchain_colorspace
ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers
Not using validation layers due to ERROR_LAYER_NOT_PRESENT while getting erupt::generated::InstanceLoader in context instance with validation
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Skipping ICD JSON.
ERROR | DRIVER: loader_icd_scan: Failed to add ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Skipping ICD JSON.
WARNING: terminator_CreateInstance: Failed to CreateInstance in ICD 3. Skipping ICD.
Loading memory info for selected device index 0...
heap size 31.0GB budget 30.9GB usage 0.0GB flags=(empty)
heap size 16.0GB budget 0.3GB usage 0.0GB flags=DEVICE_LOCAL
Runtime error: Failed determining memory budget
Subprocess status exit status: 68 parent_close_requested false
Using in-process testing method with small memory limit 0
Using in-process testing method
Runtime error: Failed determining memory budget
memtest_vulkan: INIT OR FIRST testing failed due to runtime error
press any key to continue...
You can find the output for vulkaninfo here: vulkaninfo.txt
I have also attached inxi.txt which contains some informations concerning my Linux install and my graphics gathered from the output of inxi -S and inxi -G.
Based on your troubleshooting section, I assume there might be something wrong with my vulkan installation. But as I'm still quite new in the Linux world, I'm not able to identify the issue further.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.