Vulkan crash on benchmark applications

[abhisarma7]

Hey @KonstaT,

It might sound silly, but for benchmarking purposes, I ran Antutu Benchmark 3D test, and for the gpu test, It was crashing. It says that it found the v3d 7.1.7.0 driver( Vulkan driver) but for tests such as Seasons-Vulkan and Coastline-Vulkan, it says that its not supported.

It it because of the vulkan driver in the ROM or just the app is glitching??

[abhisarma7]

Just checked with geekbench 6, the same thing, GPU tests arent working but for some reason geekbench 5 worked.
Since, both antutu and geekbench are crashing, is it a vulkan service issue?

[KonstaT]

It it because of the vulkan driver in the ROM or just the app is glitching??

Since, both antutu and geekbench are crashing, is it a vulkan service issue?

That's what logs are for so there's no need to guess. Please attach the appropriate logs (logcat in this case).

[abhisarma7]

geekbench_crash_log.txt

I've uploaded the entire log, and I ran the app at 18:31 (for time reference).

I've noticed this line -

04-10 18:31:20.586 4401 4401 F DEBUG : Abort message: 'terminating with uncaught exception of type std::runtime_error: failed to find suitable memory type'

any clue on whats causing this??

[KonstaT]

No idea TBH. You would probably need to ask Mesa/Vulkan developers. Some Vulkan features Android expects are not implemented on V3DV (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32319) but I doubt it's related to this. Attached full tombstone as I can reproduce this on Geekbench GPU test. Feel free to investigate.

tombstone_00.txt

[abhisarma7]

The geekbench 5 works fine but not 6. In the gitlab repo you've shared, I saw somewhere that they need to update the current vulkan api impl methods to the latest api impl methods ( which geekbench 6 might be using), Thus might be the reason geekbench 5 works but not 6.

Anyways, I'll debug more and figure out the exact issue.

[alexus1211]

Hi @abhisarma7 , how did you manage to get Vulkan as the default API in your build? I can see vulkan lib on the target but it is not getting used by default. Instead the build reverts back to opengl and uses it as the default for Apps that require 3D rendering.
@KonstaT any tip on how to make the surfaceflinger uses Vulkan as the default lib instead of OpenglES?

[KonstaT]

@KonstaT any tip on how to make the surfaceflinger uses Vulkan as the default lib instead of OpenglES?

By setting TARGET_USES_VULKAN := true in device.mk which translates to setting ro.hwui.use_vulkan=true in /vendor/build.prop.
https://cs.android.com/android/platform/superproject/+/android-latest-release:build/make/core/sysprop_config.mk?q=TARGET_USES_VULKAN

[alexus1211]

@KonstaT I have already tried that. I can see the boot animation but after that a black screen is shown. I have configured my build to target a 1920x720 resolution, but I am not sure if this might be an issue. Furthermore, I have seen in some posts that the renderer should be set to skiavk instead of skiagl, so I tried another build with the following set:
PRODUCT_PROPERTY_OVERRIDES +=
debug.hwui.renderer=skiavk

the result is the same (black screen after bootup). Any further ideas that could help?

[KonstaT]

Well, yeah, it would be already enabled if it worked. It's been few Android versions and several Mesa versions since I've last tested but at least it booted to UI back then (issues were with cameras and codecs).

Why it's not working? That's what the logs are for.

[alexus1211]

@KonstaT I will try to check the logs and provide some feedback. It wasn't possible in my case because I adb over wifi usually, and since no UI is there, it wasn't possible to connect a fresh build to Wifi. Will check over Ethernet and provide my findings. Thanks

[rsglobal]

mesa3d/v3dv lacks multi-queue emulation and a few AHB-related upgrades to support skia vulkan.

[KonstaT]

It wasn't possible in my case because I adb over wifi usually, and since no UI is there, it wasn't possible to connect a fresh build to Wifi. Will check over Ethernet and provide my findings.

There's an open issue on how to debug failing boot process.
#181

Still, you would rather need to ask Mesa developers about this (or maybe @rsglobal knows). I'm not a graphics driver developer.

[rsglobal]

I added missing extensions to Mesa3D to run Vulkan/HWUI. I did a smoke test/VTS, but I don't have much free time to do extensive testing.

@KonstaT ,
I noticed you picked those patches into the local Mesa3D fork. I would appreciate it if you could share your experience. Is everything ok, and we can switch to Vulkan, or is it still behaving worse than the GLES version?