[Solved] Computer crash after clicking Help->System Information.

Steam for Linux

All Discussions Artwork Videos News Guides

Steam for Linux > General Discussions > Topic Details

SebSenseGreen has Steam for Linux

7 Jan, 2023 @ 11:25pm

[Solved] Computer crash after clicking Help->System Information.

Hi, I just noticed that my computer crashes when I click on the menu "Help->System Information". It takes a few seconds and then crashes to black screen and then the desktop completely reload, as in I'm back at the login screen and all my applications are closed as if I'd restarted but i didn't. The whole thing take about 2 seconds.

I'm on Linux Manjaro KDE Plasma.
KDE Version: 5.26.4
Kernel: 6.1.1-1
CPU: Ryzen 7 2700X
RAM: 32 Gig
GPU: Radeon RX 6800XT

Thanks in advance if anyone can help.

Last edited by SebSenseGreen; 8 Jan, 2023 @ 10:34am

< >

Showing 1-9 of 9 comments

Cpt_Kopfschmerz has Steam for Linux

8 Jan, 2023 @ 1:18am

start steam from terminal and check the output

CJM

8 Jan, 2023 @ 1:58am

The Steam Deck is still on Kernel 5. It is running KDE 5.26. Might be something with the newer kernel you are running?

I think StreamOS is of the Arch family, same as Manjaro. So I would expect it to work fine other than the kernel. Unless the combination is too familiar, and Steam is looking for something in the Steam Deck's kernel.

Edit: I dug a page back and there are other reports. One reply indicated that there appears to be an audio conflict with streaming, OpenRGB was mentioned specifically.
https://github.com/ValveSoftware/steam-for-linux/issues/8923

Last edited by CJM; 8 Jan, 2023 @ 2:34am

Der_Felix

8 Jan, 2023 @ 2:50am

I have something better for system information.
Open a terminal and run

sudo pacman -S neofetch

Once you've done that, simply type "neofetch" into the terminal and you have better system information than what Steam could ever give you.

SebSenseGreen has Steam for Linux

8 Jan, 2023 @ 6:14am

Originally posted by Cpt_Kopfschmerz:
start steam from terminal and check the output

I won't see the output since when the crash occurs, everything is closed down.

I've tried it again and right after clicking on "System Information", Steam lists a bunch of stuff and end with

The runtime information tool is preparing a report, please wait...

Then it crashes.
For now, I've checked the log files and I've got a bunch, hundreds of them, of Kernel error like this:

2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x0) 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: MORE_FAULTS: 0x0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: WALKER_ERROR: 0x0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: PERMISSION_FAULTS: 0x0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: RW: 0x0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:40 vmid:2 pasid:32788, for process i386-linux-gnu- pid 18150 thread i386-linux:cs0 pid 18151) 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: amdgpu: in page starting at address 0x0000800100769000 from client 0x12 (VMC) [...] 2023-01-08 9:01 A.M. kernel [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec_0 timeout, signaled seq=12, emitted seq=14 2023-01-08 9:01 A.M. kernel [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 2023-01-08 9:01 A.M. kernel amdgpu 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0x46b300 flags=0x0000] 2023-01-08 9:01 A.M. kernel snd_hda_intel 0000:0a:00.1: spurious response 0x0:0x0, last cmd=0x1f0500

Originally posted by CJM:
The Steam Deck is still on Kernel 5. It is running KDE 5.26. Might be something with the newer kernel you are running?

I think StreamOS is of the Arch family, same as Manjaro. So I would expect it to work fine other than the kernel. Unless the combination is too familiar, and Steam is looking for something in the Steam Deck's kernel.

Edit: I dug a page back and there are other reports. One reply indicated that there appears to be an audio conflict with streaming, OpenRGB was mentioned specifically.
https://github.com/ValveSoftware/steam-for-linux/issues/8923

Yeah, I had an old kernel and the updater started to complain that my kernel wasn't supported anymore and to change it. So I did. I haven't checked the "System Information" in ages, so I don't know if it has to do with the kernel. And to be fair, I just picked the highest number and called it a day.
As for the other reports, I'll go check that out. Thanks.

Originally posted by The Nintendo Guy:
I have something better for system information.
Open a terminal and run
sudo pacman -S neofetch
Once you've done that, simply type "neofetch" into the terminal and you have better system information than what Steam could ever give you.

I want the Steam system info for ProtonDB. I'm pretty sure they can't take whatever neofetch spews out.

Last edited by SebSenseGreen; 8 Jan, 2023 @ 6:17am

CJM

8 Jan, 2023 @ 7:35am

Originally posted by SebSenseGreen:
The runtime information tool is preparing a report, please wait...

Then it crashes.
For now, I've checked the log files and I've got a bunch, hundreds of them, of Kernel error like this:

amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS amdgpu: PERMISSION_FAULTS : amdgpu: MAPPING_ERROR: snd_hda_intel 0000:0a:00.1: spurious response

Stack trace? Sound card driver returned bad data, the Steam Client error handling failed and it crashed, so the amdgpu driver noticed Steam just disappeared on it? Flows with the OpenRGB issue others reported.

Your old kernel might not have been supported, but I think the sound driver might not be up to snuff with the new kernel.

SebSenseGreen has Steam for Linux

8 Jan, 2023 @ 7:41am

Originally posted by CJM:
Stack trace? Sound card driver returned bad data, the Steam Client error handling failed and it crashed, so the amdgpu driver noticed Steam just disappeared on it? Flows with the OpenRGB issue others reported.

Your old kernel might not have been supported, but I think the sound driver might not be up to snuff with the new kernel.

OMG, thanks I wouldn't have been able to decipher that in a million year. I'm going to downgrade my kernel in that case.

Thanks for the assist !

SebSenseGreen has Steam for Linux

8 Jan, 2023 @ 10:34am

Just as an update, downgrading the kernel to 6.0.15-1 did the trick. The computer doesn't crash anymore and I can get all the information from the System Information in Steam.

Thanks for the help guys, really appreciated.