So it seems possible that for some reason or another the package may be needed. Though I have not seen such an example, and the reference is a bit cryptic.
I think this may be because AMD’s default boot parameter support on Linux isn’t great… After all, this issue has been around for 6 years and still appears on the latest CPUs. So, the only option seems to be to disable the C6 state through a different method during boot. Given that someone has tried configuring this parameter without success, I will try it later today and observe if any issues arise. When I’m at home, this problem almost always occurs, but interestingly, it rarely happens when I bring the computer to the office. Perhaps it’s because the power consumption isn’t as “low” at the office.
What I mean is that just configuring processor.max_cstate=5 does not work, but only using disable-c6.service does. So I turned off disable-c6.service in order to test processor.max_cstate=5.
Oh, by the way, after I executed sudo mkinitcpio -P, the startup screen was no longer the interface I configured. It was replaced by a small circle, but the shutdown interface still took effect. Is there a solution for this?
at least on my system i decided software was a bad way to do this since my b650 has an option to disable cstates in the power efficiency section, cheers
The likelihood of recent system freezes has reduced significantly, but it still occurs at night. It seems that disabling C6 through software during boot isn’t a complete solution.