Comment 801 for bug 1690085

I can confirm that in my case, all the suggested alternatives in this
thread didn't work (the ones that were applicable to my use-case anyway).

In the end, I threw my hands up and did an RMA. And that was over a
month ago. It seems to have solved the isssue. The processor I had
previously and its replacement were different batches; the former being
from 2019 and the latter from Feb. 2020. It seems to me that AMD ironed
out some issues with processors and I got lucky with the replacement. Or
it could just be some tiny variations in fabrication. I can never be sure.

But my machine has been up since the RMA without any crashes.

On 9/17/20 7:25 AM, <email address hidden> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> Ewerton Urias (<email address hidden>) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |<email address hidden>
>
> --- Comment #719 from Ewerton Urias (<email address hidden>) ---
> Hello everyone.
>
> I apologize for my English, I'll try to communicate.
>
> I did a hardware upgrade in November 2019 (Intel for AMD), my current
> hardware
> is this:
>
> ------------------------------------------------
> ASUS TUF B450-PRO GAMING
> Ryzen 5 1600 Six-Core (BIOS always updated)
> GeForce GTX 960 4 GB 128 Bits
> Corsair 650w
> Corsair LPX 16 GB 2666
> ------------------------------------------------
>
> During the first few weeks, I noticed reboots and freezes, and after a few
> months of research, I found an alternative solution, which is just to add
> "processor.max_cstate=1" to Grub.
>
> After I did this, my computer went 6 months without rebooting and/or
> freezing.
>
> Yesterday I removed this parameter from Grub, to see what the result would
> be,
> and it happened, I had a reboot and a freeze, it means that
> "processor.max_cstate=1" is a solution for me.
>
> The reason I'm here is to understand the root of the problem, to correct it
> correctly, I'll soon test "Power Supply Idle Control" and "Global C-State
> Control" in BIOS, but I have seen that for some users it didn't work.
>
> I'm trying to read all of your comments (there are many), but skipping to the
> last comments, it seems that there is still no solution to this problem, and
> this makes me very sad.
>
> I don't know anything about hardware, could someone explain to me, in a
> layman's way, the difference between using "processor.max_cstate=1",
> "processor.max_cstate=5", "Power Supply Idle Control" and "Global C-State
> Control"?
>
> I thank you for your patience.
>