Steam's system information triggers crash
When using steam's system information tool the system crashes after a few seconds.
I crashes on 6.3.0, 6.1.26 on both kwin_x11 and kwin_wayland. However on 5.15.109 it works fine.
My notebook has amd+nvidia using prime but there are other reports in valve, mesa and manjaro forums.
https://github.com/ValveSoftware/steam-for-linux/issues/9267
https://forum.manjaro.org/t/steam-native-getting-system-information-crashes-the-gpu-driver/131748/4
System information
System:
Kernel: 6.3.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3-x86_64
root=UUID=9e8a1329-5938-4b09-8479-cbfdb008bacd rw rootflags=subvol=@ quiet
udev.log_priority=3 nvidia-drm.modeset=1
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_wayland vt: 2
dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82JU v: Legion 5 15ACH6H
CPU:
Info: model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000C
Graphics:
Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1,
DP-2, HDMI-A-1, eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: none
bus-ID: 06:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 40.0 C
Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,amdgpu display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (renoir LLVM
15.0.7 DRM 3.52 6.3.0-1-MANJARO) direct-render: Yes
journalctl -p err -b -1 --no-pager
Journal file /var/log/journal/f78631a4a95946c789aa2ca77170c8a4/user-1000@0005fb7feaefdf0a-e49a055ebdd0a34a.journal~ is truncated, ignoring file.
may 12 11:29:16 santiago-82ju kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
may 12 11:29:16 santiago-82ju kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
may 12 11:29:16 santiago-82ju systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
may 12 11:29:16 santiago-82ju systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
may 12 11:29:17 santiago-82ju kernel:
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init vcp plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init mcp plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init bap plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: Failed to set mode: Blocked through rfkill (0x12)
may 12 11:29:19 santiago-82ju sddm[743]: Failed to read display number from pipe
may 12 11:29:25 santiago-82ju bluetoothd[673]: Failed to set mode: Blocked through rfkill (0x12)
may 12 11:29:28 santiago-82ju wpa_supplicant[895]: bgscan simple: Failed to enable signal strength monitoring
may 12 11:30:46 santiago-82ju systemd-coredump[3317]: [🡕] Process 3311 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 3311:
#0 0x00000000f5f9b3cf n/a (libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
#1 0x00000000f5f1fa0d n/a (libnvidia-glcore.so.530.41.03 + 0x1971a0d)
#2 0x00000000f5f21fb3 n/a (libnvidia-glcore.so.530.41.03 + 0x1973fb3)
#3 0x00000000f5f231af n/a (libnvidia-glcore.so.530.41.03 + 0x19751af)
#4 0x00000000f766ae35 n/a (libGLX_nvidia.so.0 + 0x94e35)
#5 0x00000000f7c09680 n/a (libvulkan.so.1 + 0x27680)
#6 0x00000000e7772c57 n/a (/home/santiago/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so + 0x15c57)
ELF object binary architecture: Intel 80386
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32790, for process i386-linux-gnu- pid 3327 thread i386-linux:cs0 pid 3328)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x0000800100768000 from IH client 0x12 (VMC)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00143851
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: VCN (0x1c)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x1
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x5
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: RW: 0x1
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32790, for process i386-linux-gnu- pid 3327 thread i386-linux:cs0 pid 3328)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x0000800100769000 from IH client 0x12 (VMC)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: RW: 0x0
may 12 11:30:47 santiago-82ju systemd-coredump[3934]: [🡕] Process 3928 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 3928:
#0 0x00007f63fda28dd8 n/a (libnvidia-glcore.so.530.41.03 + 0x1990dd8)
#1 0x00007f63fd9a9d3f n/a (libnvidia-glcore.so.530.41.03 + 0x1911d3f)
#2 0x00007f63fd9ac675 n/a (libnvidia-glcore.so.530.41.03 + 0x1914675)
#3 0x00007f63fd9ad2fb n/a (libnvidia-glcore.so.530.41.03 + 0x19152fb)
#4 0x00007f6400b768f0 n/a (libGLX_nvidia.so.0 + 0x9c8f0)
#5 0x00007f64013acc06 n/a (libvulkan.so.1 + 0x23c06)
#6 0x00007f63ffe95257 n/a (/home/santiago/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so + 0x19257)
ELF object binary architecture: AMD x86-64
may 12 11:30:50 santiago-82ju systemd-coredump[5333]: [🡕] Process 5327 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 5327:
#0 0x00000000f5c4e3cf n/a (/run/host/usr/lib32/libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
ELF object binary architecture: Intel 80386
may 12 11:30:51 santiago-82ju systemd-coredump[6496]: [🡕] Process 6490 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 6490:
#0 0x00007f7fb6828dd8 n/a (/run/host/usr/lib/libnvidia-glcore.so.530.41.03 + 0x1990dd8)
ELF object binary architecture: AMD x86-64
may 12 11:30:53 santiago-82ju systemd-coredump[7649]: [🡕] Process 7643 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 7643:
#0 0x00000000f5cfb3cf n/a (/run/host/usr/lib32/libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
ELF object binary architecture: Intel 80386
may 12 11:30:54 santiago-82ju systemd-coredump[8613]: [🡕] Process 8607 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 8607:
#0 0x00007f2bd4628dd8 n/a (/run/host/usr/lib/libnvidia-glcore.so.530.41.03 + 0x1990dd8)
ELF object binary architecture: AMD x86-64
may 12 11:33:39 santiago-82ju systemd-logind[677]: Failed to start autovt@tty2.service: Transaction for getty@tty2.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).