Mesa not playing well with Hogwarts Legacy
Description
I launched Hogwarts Legacy, and frequently enough, the entire desktop would crash randomly. I find that this happens more often after waking up the desktop from sleep, as the same thing happens with Halo: Infinite.
https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1427138732
Screenshots/video files
I couldn't take a screenshot because the entire desktop already crashed. The screen goes black, but the background audio still works.
Log files (for system lockups / game freezes / crashes)
- journal output from 220219-1511.txt
- X11:
- Old: steam-990080.log
- New (happens without needing to sleep): steam-990080.log
- Wayland: steam-990080.log
- Backtrace (for crashes)
- Output of
dmesg
- Hang reports: Run with
RADV_DEBUG=hang
and attach the files created in$HOME/radv_dumps_*/
Didn't work. I added it on the game's launch options
Steps to reproduce
It happens randomly, but I do notice a pattern:
- Put the PC to sleep for a significant amount of time
- Run the game
Not much help, I know, but that's what I notice. Sometimes, it takes a while, and sometimes, it happens in less than an hour
System information
$ inxi -GSC -xx
System:
Host: Y4M1-II Kernel: 6.1.12-1-liquorix-amd64 arch: x86_64 bits: 64
compiler: gcc v: 12.2.0 Desktop: KDE Plasma v: 5.27.0 tk: Qt v: 5.15.6
wm: kwin_x11 dm: SDDM Distro: Ubuntu 22.10 (Kinetic Kudu)
CPU:
Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3
level: v3 rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 3719 high: 4550 min/max: 2200/4950 boost: enabled
cores: 1: 3700 2: 3592 3: 3595 4: 3700 5: 3589 6: 3700 7: 3640 8: 3700
9: 3700 10: 3700 11: 3700 12: 4550 13: 3700 14: 3700 15: 3700 16: 3700
17: 3700 18: 3700 19: 3700 20: 3700 21: 3700 22: 3700 23: 3700 24: 3700
bogomips: 177613
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: ASRock
driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports:
active: DP-1,DP-3 empty: DP-2,HDMI-A-1 bus-ID: 0d:00.0 chip-ID: 1002:73bf
Device-2: NVIDIA GA104 [GeForce RTX 3060 Ti] vendor: eVga.com.
driver: N/A arch: Ampere pcie: speed: 16 GT/s lanes: 8 bus-ID: 0e:00.0
chip-ID: 10de:2486
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 6400x2160 s-dpi: 96
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,top-left
model: BenQ EW3270U res: 3840x2160 dpi: 140 diag: 801mm (31.5")
Monitor-2: DP-3 mapped: DisplayPort-2 pos: primary,bottom-r
model: VG27AQ1A res: 2560x1440 dpi: 109 diag: 685mm (27")
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.6 DRM 3.49
6.1.12-1-liquorix-amd64) v: 4.6 Mesa 23.0.0-rc5 direct render: Yes
The NVIDIA GPU can be ignored as I'm using that for my VMs.
If applicable
- Xserver version: (
sudo X -version
)
$ sudo X -version
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
Current Operating System: Linux Y4M1-II 6.1.12-1-liquorix-amd64 #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.1-25ubuntu1~kinetic (2023- x86_64
Kernel command line: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0xffffffff quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.1.12-1-liquorix-amd64
xorg-server 2:21.1.4-2ubuntu1.5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
- DXVK version: not sure how
- Wine/Proton version: 7.0-6
Regression
Not sure, TBH. I tried 22.2.5-0ubuntu0.1
from the official Ubuntu repo & 23.0.0~rc5+git2302172054.2b8579c7ab2~k~mesarc1
from the mesarc PPA.
API captures (if applicable, optional)
Consider recording a GFXReconstruct (preferred), RenderDoc, or apitrace capture of the issue with the RADV driver active. This can tremendously help when debugging issues, but you're still encouraged to report issues if you can't provide a capture file.
Further information (optional)
Does the issue reproduce with the LLVM backend (RADV_DEBUG=llvm
) or on the AMDGPU-PRO drivers?
Does your environment set any of the variables ACO_DEBUG
, RADV_DEBUG
, and RADV_PERFTEST
?