You are not logged in.
When I updated to the 5.10 kernel after I logged in, about a minute later my machine rebooted. It did this with both the vanilla kernel, and the zen kernel. After downgrading back to the 5.9 kernel the issue didn't persist.
No warning, nothing in the logs, just reboot like a hardreset.
The last journalctl with the 5.10.4 kernel: https://pastebin.com/gBLxPzjA
I tried turning NTP off, didn't change a thing.
Tried the 5.11-rc2 kernel, did the same thing.
Offline
Ryzen.
Did yo try the LTS kernel?
Chances are BIOS or µcode, https://bbs.archlinux.org/viewtopic.php?id=257371
Offline
Based on purely anecdotal evidence (I happen to have a system where I know that that is the cause for instant shutdowns not unlike what you describe), try disabling snd_hda_intel's power save with e.g. a file in /etc/modprobe.d/sound.conf
options snd_hda_intel power_save=0
Offline
Also ALC1220?
Offline
Ryzen.
Did yo try the LTS kernel?
Chances are BIOS or µcode, https://bbs.archlinux.org/viewtopic.php?id=257371
I am running the latest (3102) BIOS, and have amd-ucode working.
Based on purely anecdotal evidence (I happen to have a system where I know that that is the cause for instant shutdowns not unlike what you describe), try disabling snd_hda_intel's power save with e.g. a file in /etc/modprobe.d/sound.conf
options snd_hda_intel power_save=0
That didn't work.
Offline
Did yo try the LTS kernel?
I am using it right now. But I want the latest kernel and I don't see any reason other than this issue, why I couldn't.
Last edited by Holorum (2021-01-07 16:15:23)
Offline
You want to know whether the kernel update was actually the trigger.
Offline
You want to know whether the kernel update was actually the trigger.
I am pretty sure, yes: With the 5.9 kernels and the 5.4 LTS kernel the system is stable.
Offline
Is the behavior somewhat deterministic? ("after I logged in, about a minute later")
What if you don't log in?
What if you only boot the multi-user.target?
If so, what if you chose a different session (eg. openbox, I assume you're currently using KDE/plasma)?
Offline
It's one minute after decrypting my root partition.
It happens even if I log in.
It happens even when only booting to multi-user.target.
It happens when I switch to KDE Plasma (I use i3-gaps normally).
Disabling sddm didn't help either.
I tried with the new 5.10.5, didn't help.
Last edited by Holorum (2021-01-07 19:18:13)
Offline
The multi-user.target makes GPU and RAM unlikely, see https://wiki.gentoo.org/wiki/Ryzen#Rand … mce_events
Despite there're no MCE errors in the journal, try to limit the C-States…
Offline
Limiting the C-states didn't help.
No luck with the kernel parameter
idle=nomwait
either.
And disabling "Power Supply Idle Control" wasn't any better.
Offline