Comment 44 for bug 1939966

So, out of pure frustration, I wondered if maybe it was the particular SSD slot, so I decided to simply switch my SSDs across the slots on my motherboard (because the Kubuntu installation never crashed). Suddenly, now, that one was crashing, and the Xubuntu installation worked fine (for a while). so I thought it was the SSD slot. Then, the "good" slot started crashing randomly, too.

I started looking around for my specific computer, and it turns out that the "soft lockup" is from a misconfiguration in the grub setup. I thought to myself, "I haven't touched my grub. The only time I ever did anything was the `sudo apt dist-upgrade` about three weeks ago." And then it hit me: the crashes started about a day or two after I did a dist-upgrade. So I started looking around, and I found this:

https://github.com/jfinancial/linux/blob/main/AMD_Linux_Build.md

and subsequently this:

https://askubuntu.com/questions/1234299/amd-ryzen-5-3600-ubuntu-20-04-problems/1241636#1241636

so I went into /etc/default/grub and changed the line to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=assign-busses apicmaintimer idle=poll reboot=cold,hard"

and did a `sudo update-grub`. So far, my computer has an uptime of around 13 hours, so this is looking promising. Also, I am never, ever, ever updating my kernel ever again, ever. Every time I do, something absolutely vitally, crucially important breaks. This is especially true about Arch and all Arch-based distros (which I'll never use again).

I'll try leaving my computer turned on for a week and see if changing that grub line helps. Here's to hoping.