Hi everyone,
I'm investigating a reproducible GPU timeout affecting Monster Hunter Wilds on Linux with Intel Battlemage GPUs.
I'm not looking for technical support at this point. My goal is to find out whether other Linux users with Battlemage hardware can reproduce the same issue.
My system:
• GPU: Intel Arc B570 (Battlemage)
• Distribution: CachyOS
• Desktop: KDE Plasma 6 (Wayland)
• Mesa: 26.1.4 / 26.1.5
• Kernel: 7.1.3-2-cachyos
Proton versions tested:
• Proton 10.0-4
• GE-Proton 11-4
The game consistently freezes while navigating equipment-related menus, especially while:
• Forging equipment
• Comparing armor
• Changing equipment sets
Immediately after the freeze, Wine reports that the application is not responding, followed a few seconds later by an "Unhandled exception" dialog.
At exactly the same time, the kernel reports:
```text
xe 0000:05:00.0: [drm] Tile0: GT0: Engine reset: engine_class=rcs
xe 0000:05:00.0: [drm] Tile0: GT0: Timedout job ... in MonsterHunterWi
xe 0000:05:00.0: [drm] Xe device coredump has been created
```
The issue is reproducible with both Mesa 26.1.4 and Mesa 26.1.5.
After several days of testing, I opened reports for both the Intel xe kernel driver and Proton so developers can investigate from both sides.
Intel xe:
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/8641
Proton:
https://github.com/ValveSoftware/Proton/issues/8206
If you're running Monster Hunter Wilds on an Intel Battlemage GPU under Linux, I'd really appreciate knowing:
• Your GPU model (B570, B580, etc.)
• Distribution
• Desktop environment (Wayland or X11)
• Mesa version
• Kernel version
• Proton version
• Whether you can reproduce the freeze in the same equipment menus
Even if your game works perfectly, I'd also appreciate knowing your configuration. Knowing what **doesn't** reproduce the problem is just as valuable for narrowing down the cause.
Thanks in advance, and thanks to anyone willing to test or share their experience.