Re: Issues with Chromium/Vulkan after upgrading vulkan to 1.2.190

Pete Wright <[email protected]> writes:

> hey there -
> i am having an issue running chrome on an i915 intel system under
> current after upgrading my vulkan packages to v1.2.190.

Upgrading from which version? v1.2.189 or earlier one?
Besides, Chromium 92 doesn't enable Vulkan renderer by default.

> $ vulkaninfo
> ERROR at
> /wrkdirs/usr/ports/graphics/vulkan-tools/work/Vulkan-Tools-1.2.190/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfacePresentModesKHR
> failed with ERROR_UNKNOWN

Did you try to reboot? Sometimes GPU is wedged without triggering GPU reset.
Does vulkaninfo and vkcube-display work fine on KMS console (e.g., ttyv0)?

> this was working before i upgraded to latest packages (which vulkan
> 1.2.190 were part of), curious if others are seeing similar behavior,
> or if there is some additional debugging i can do on my end?

I can't reproduce on Skylake with i915kms from drm-current-kmod with
either mesa-dri or mesa-devel. Tested with chromium-92.0.4515.159_1
after enabling Vulkan in about://flags and confirming Vulkan is used
by adjusting environ(7) with VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay.

Can you reproduce after downgrading just vulkan-headers + vulkan-loader?
vulkan-loader alone v1.2.189 -> v1.2.190 only had one functional change
https://github.com/KhronosGroup/Vulkan-Loader/commit/5661252091f2
while the rest are in tests which aren't hooked in ports/ yet.

For debugging the following may provide some clues:

$ vidcontrol -s 1 </dev/ttyv0 # or Ctrl+Alt+F1
$ sysctl kern.msgbuf_show_timestamp=1
$ sysctl hw.dri.debug=$((0x01 | 0x02 | 0x04 | 0x08 | 0x10 | 0x20 | 0x80 | 0x100))
$ vulkaninfo
$ sysctl hw.dri.debug=0
$ sysctl kern.msgbuf_show_timestamp=0
$ dmesg | sed -n '/\[drm/,$p' >/tmp/vulkainfo.drm-debug.log