Comment 800 for bug 1690085

Revision history for this message
In , ewerton.urias (ewerton.urias-linux-kernel-bugs) wrote :

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.