Project

General

Profile

Actions

Emulator Issues #11972

closed

Vulkan backend breaks on Surface Pro 7

Added by Anonymous about 4 years ago. Updated almost 4 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

VideoBackends\Vulkan\VulkanLoader.cpp:220 E[Video]: (SubmitCommandBuffer) vkQueueSubmit failed: (-4: VK_ERROR_DEVICE_LOST)
Common\MsgHandler.cpp:115 E[MASTER]: Question: Failed to submit command buffer.

Game Name?

Metroid Prime Trilogy (Issue may be present in other games as well, but I do not have others to test)

Game ID? (right click the game in the game list, Properties, Info tab)

R3ME01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

823df1c3c425f1383529f368f6479359

What's the problem? Describe what went wrong.

When starting Metroid Prime Trilogy from a save point or save state, an error message stating "Failed to submit command buffer" appears then the video freezes but the audio continues. Issue occurs with both Synchronous and Asynchronous (Ubershaders) but does not occur with Synchronous (Ubershaders).

What steps will reproduce the problem?

Issue reproduction requires an 10th Gen Intel Iris Plus gpu with driver version .7584 or higher installed as that is what the Surface Pro 7 has installed.

Start Dolphin 5.0 - xxxxx
Choose Vulkan as backend and Intel Iris Plus as adapter.
Start Metroid Prime Trilogy and load from a save point or save state.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-11622

Is the issue present in the latest stable version?

Quite likely as I was able to replicate the issue consistantly going backwards through the developer builds.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

I was able to replicate the issue back to 5.0-10662 before I stopped testing.

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

What are your PC specifications? (CPU, GPU, Operating System, more)

Surface Pro 7
Intel Core i7-1065G7
Intel Iris Plus
16.0 GB Ram
256 GB SSD - KBG40ZPZ256G Toshiba Memory

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

The following errors are logged by Dolphin:

VideoBackends\Vulkan\VulkanLoader.cpp:220 E[Video]: (SubmitCommandBuffer) vkQueueSubmit failed: (-4: VK_ERROR_DEVICE_LOST)
Common\MsgHandler.cpp:115 E[MASTER]: Question: Failed to submit command buffer.

The issue does not occur when using Microsoft's Intel Iris Plus driver version .7101.

Actions #1

Updated by Anonymous about 4 years ago

Oops... I didn't mean to duplicate the error message at the beginning on my bug report.

Actions #2

Updated by Anonymous about 4 years ago

Not sure how I missed it when going through the current and closed issues, but this bug happened before almost 3 years ago with AMD Polaris gpus.

https://bugs.dolphin-emu.org/issues/9879

Actions #3

Updated by Stenzek about 4 years ago

Not saying it's definitely a driver bug, and not something on our end, but I wouldn't be surprised if it was. Intel's driver up until recently would crash when booting because despite advertising support for dual-source blend, clearly hadn't tested any pipelines which used them because they'd kill it with a null pointer access.

Does it only happen on 10th generation GPUs? I don't have anything this recent, the most recent iGPU I have access to is a Gen9.5/Kaby Lake.

Also could be worth trying the same save state on another system with a different GPU vendor.

Actions #4

Updated by Stenzek about 4 years ago

Also, FWIW, "device lost" is just a general error basically meaning the GPU did something naughty (crashed), and the driver reset it. The fact that the Polaris bug also resulted in device lost doesn't necessarily mean the causes are related, just that the result is the same in the end.

Actions #5

Updated by Anonymous about 4 years ago

I'd love to think it was strictly a driver issue, but that wouldn't explain why the problem doesn't occur with synchronous ubershaders. And yet, Intel did just add support for the Vulkan 1.2 api, maybe that could be the cause.

Give the Gen 9.5 a shot and see what happens. They use the same DCH driver branch as the Gen 10. It would help narrow down the cause. Unfortunately, I do not have any other systems to test with.

Interestingly, I've been using Dolphin with Intel gpu laptops and Surface Pros since 2010 and never had an issue until now.

Actions #6

Updated by Stenzek about 4 years ago

Ubershaders generate a different set of pipelines/commands, it's possible that it won't trigger the bug due to that.

I won't be able to investigate it for a few weeks, but if someone else has compatible hardware and wants to check that would be helpful.

Actions #7

Updated by Anonymous about 4 years ago

Hey Stenzek, I just got my hands on an HP envy with a 10th gen i7 intel cpu and Iris Plus GPU at work. Don't have my dolphin stuff with me today, will test tomorrow to see if I can reproduce the issue on that device.

I am curious how much of a difference there is between ubershaders (asynchronous) and ubershaders (synchronous) that causes one to work fine and one to freeze up.

Actions #8

Updated by Anonymous almost 4 years ago

Please close this bug report. The problem was caused by issues in the drivers for the Iris Plus GPU. It has been fixed in the last 2 versions from Intel, Microsoft just needs to play catchup with their own driver version.

Actions #9

Updated by JosJuice almost 4 years ago

  • Status changed from New to Invalid
Actions

Also available in: Atom PDF