GpuZelenograd / memtest_vulkan

Vulkan compute tool for testing video memory stability
https://github.com/GpuZelenograd/memtest_vulkan/blob/main/Readme.md
zlib License
262 stars 12 forks source link

Nvidia 1GB Quadro K600 (Video-Card) - INIT OR FIRST testing failed due to runtime error #34

Open panorain opened 4 months ago

panorain commented 4 months ago

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

galkinvv commented 4 months ago

Hi. Unfortunately memtest_vulkan does not support Kepler-base nvidia GPUs (due to their memory organization).

Typically they error-out with This device lacks support for DEVICE_LOCAL+HOST_COHERENT memory type, but for your case there was an earlier problem, so an error message is a bit obscure. I'll try to imporove error messages, but there is no plans on supporting Nvidia Kelper-based GPUS.

panorain commented 4 months ago

Hey, thank you for responding with your message. Is memtest_vulcan still helpful to run on the Nvidia Kepler-based GPU here? I select: -> 2: Bus=0x00:00 DevId=0x0000 API 1.3.267 ver1 8GB llvmpipe (LLVM 17.0.6, 128 bits)

It seems like the test is runs with 1 error shown before testing starts: ERROR: loader_validate_layers: Layer 0 does not exist in the list of available layers

Is that a helpful test for the Nvidia Kelper-based GPU here?

galkinvv commented 4 months ago

The "8GB llvmpipe" is a software-based vulkan implementation/emulation executed on the main CPU. It is a some (not effective I suppose) CPU+main memory test, but it does not touch GPU in any way.

(those layer-related erros/info are motly for debugging, shown only in verbose mode, just ignore them).