Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
22818 Discussions

Validation layer reports VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT instead of VK_DEBUG_REPORT_OBJECT_TYPE_COMMAND_POOL_EXT

Frost__Nathan
Beginner
1,464 Views

System Setup Information:
-----------------------------------------

System Used: Razer Blade Stealth
CPU SKU: Kaby Lake-U/Y Intel Core i7 8550U
GPU SKU: UHD 620 
Processor Line: U-Series
System BIOS Version: Razer 1.01, 9/12/2017
Graphics Driver Version: 26.20.100.6890
GOP/VBIOS Version: 9.0.1068
Operating System: Windows 10
OS Version: Version 1803 OS Build 17134.765
API: Vulkan SDK 1.1.106.0 installed on Windows -- Vulkan Version reported by Intel UHD Graphics Control Panel = 1.1.103 
Occurs on non-Intel GPUs?: Unsure

Steps to Reproduce:
-------------------------------
In one Cpu thread, call vkQueueSubmit() with a command buffer that was created from command pool A; in another Cpu thread, call vkQueueSubmit() with another command buffer also created from command pool A.

Expected Results:
-------------------------------

This violation of the Vulkan spec should produce a validation error callback with its VkDebugReportObjectTypeEXT argument set to VK_DEBUG_REPORT_OBJECT_TYPE_COMMAND_POOL_EXT.

Actual Results:
-------------------------------

The validation error callback sets its VkDebugReportObjectTypeEXT argument to VK_DEBUG_REPORT_OBJECT_TYPE_UNKNOWN_EXT.

 

0 Kudos
0 Replies
Reply