You are not logged in.
Hello. I have bought and threw together a new PC specifically to use Linux on it.
The first time the crash happened was when I was installing a game in Lutris.
After that, random crashes kept on happening.
I tried checking logs using 'journalctl' and 'dmesg', but I am still inexperienced enough to know what the hell I am looking at.
CPU: AMD Ryzen 7 5700G with Radeon Graphics (16) @ 3.800GHz
GPU: AMD ATI Radeon RX 6700/6700 XT / 6800M
OS: Arch Linux x86_64
Kernel: 5.16.16-zen1-1-zen
This is the last log: https://www.toptal.com/developers/haste … abi.apache
Any help would be much appreciated.
Edit for anyone experiencing the same issue: the shutdown/reboot and freezing after sleep is still there, but the random crashes have been a hardware issue. My ram speed was set to auto in BIOS, and the pc crashed when it reached 3200mhz. When i dug a bit more i found that I bought ram sticks that are incompatible with the ryzen thing, whatever. I have set it to 3133mhz and now it works fine.
Last edited by zbejas (2022-03-26 21:39:16)
Offline
This is a bit of a longshot, but I've been having similar issues after upgrading to the 5.16.16 kernel two days ago.
I'd try switching to the linux-lts package (you should also probably install linux-lts-headers if you've installed any dkms packages from the AUR).
If the issue persists, try running journalctl and filtering the output:
Use the --boot flag - this will only print messages from the current boot. You can also pass it a number --boot=-1 to print messages from the last boot (useful when investigating a previous crash).
Use the --priority=5 flag - this will only print messages with "notice" severity and up. If there's still too much output, try --priority=3 which will only print errors. If you find something that looks promising, try removing the flag and finding the error again to see if there are any relevant non-error messages around it.
Finally, if you can't find anything, the system continues to behave weirdly and taking into account that it's a newly built machine, it might be a hardware issue.
I'd start with installing and running [memtest86](https://aur.archlinux.org/packages/memtest86-efi) (I think there's also a liveusb option) - keep in mind that the full test will probably take several hours though.
Good luck!
Offline
This is a bit of a longshot, but I've been having similar issues after upgrading to the 5.16.16 kernel two days ago.
I'd try switching to the linux-lts package (you should also probably install linux-lts-headers if you've installed any dkms packages from the AUR).If the issue persists, try running journalctl and filtering the output:
Use the --boot flag - this will only print messages from the current boot. You can also pass it a number --boot=-1 to print messages from the last boot (useful when investigating a previous crash).
Use the --priority=5 flag - this will only print messages with "notice" severity and up. If there's still too much output, try --priority=3 which will only print errors. If you find something that looks promising, try removing the flag and finding the error again to see if there are any relevant non-error messages around it.Finally, if you can't find anything, the system continues to behave weirdly and taking into account that it's a newly built machine, it might be a hardware issue.
I'd start with installing and running [memtest86](https://aur.archlinux.org/packages/memtest86-efi) (I think there's also a liveusb option) - keep in mind that the full test will probably take several hours though.
Good luck!
My last log showed this: https://pastebin.com/dfd0LvDQ
This happened on lts. I've been hopping kernels for a while now, I think this has something to do with xorg, since this time it crashed when running Plex, which runs with xwayland (crashes also happen when using X11 instead of Wayland, but more often (i think)).
And again while playing a game in Lutris: https://pastebin.com/Y9u7pZbe (linux-lts). And then multiple crashes right after that.
Last edited by zbejas (2022-03-25 22:01:17)
Offline