Red Faction: Armageddon (55110) hangs Intel GPU with Vulkan

System information

System:
  Host: voyager Kernel: 5.8.0-64-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Gnome 3.36.9 wm: gnome-shell dm: GDM3 
  Distro: Ubuntu 20.04.2 LTS (Focal Fossa) 
CPU:
  Topology: Dual Core model: Intel Core i5-5300U bits: 64 type: MT MCP 
  arch: Broadwell rev: 4 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 18357 
  Speed: 798 MHz min/max: 500/2900 MHz Core speeds (MHz): 1: 798 2: 798 
  3: 799 4: 793 
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:1616 
  Display: wayland server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa compositor: gnome-shell resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) 
  v: 4.6 Mesa 21.1.6 - kisak-mesa PPA direct render: Yes

If applicable

DXVK version: 1.9
Wine/Proton version: 6.3-5

Describe the issue

The game "Red Faction: Armageddon" freezes when the user "repairs" something in the game. This also causes the desktop to hang for a while. After a couple of seconds (~10s) I am able to interact with the desktop again, but the game stays frozen with only the audio playing. This does not always happen, but it happens almost always. It should be easily reproducible.

See https://github.com/ValveSoftware/Proton/issues/848#issuecomment-890371528 for the original proton report.

This seems to be only an issue for the 5th gen Intel GPUs (Broadwell) but not the 6th gen.

Regression

It does seem to work for other users and on newer hardware (6th gen Intel GPUs).

Log files as attachment

I am attaching a more recent proton log (mesa 21.1.6): steam-55110.log. According to the log, the GPU hangs in anv_device.c:

MESA-INTEL: error: ../src/intel/vulkan/anv_device.c:3543: GPU hung on one of our command buffers (VK_ERROR_DEVICE_LOST)
err:   DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST

The same GPU hang issue (GPU hung on one of our command buffers) is present in the old log from the original proton report (mesa 21.0.3), it just appears at a different line in the same source file.

Any extra information would be greatly appreciated

The related issues #3092 #4837 #4914 #4945 (closed) report a similar error (VK_ERROR_DEVICE_LOST) but in a different part of the driver (anv_batch_chain.c). This issue is the first that reports the VK_ERROR_DEVICE_LOST issue in anv_device.c.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information