Comment 810 for bug 1690085

Created attachment 294183
attachment-20815-0.html

Hi Ewerton.

This might be a side effect and kind of unrelated with the bug. Since YMMV
and this can wreck your HW please read this as an anecdotal experience.
When you overclock RAM you need to change other stuff in order to stabilize
the system. This video from AMD people helped me get 3000Mhz with no
issues. Before this video I was wasting -part of- the money I paid for the
sticks running at 2666. This was with an Ab350m-ds3h (BIOS F31) and a Ryzen
2700X.

  https://www.youtube.com/watch?v=vZgpHTaQ10k

BTW, Memtest86 helped me a lot here. It would detect an invalid
configuration in a second. I was happy after it ran a few times and I
didn't have any issues after that. Since then I switched to a recent
motherboard and the RAM was detected automatically.

On Wed, Dec 16, 2020 at 9:22 PM <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> --- Comment #726 from Ewerton Urias (<email address hidden>) ---
> I'm here again, after my first comment (Comment 719).
>
> I have Ryzen 5 1600 (UA 1843PGS), and I come to report some news about my
> case.
>
> I have 2x8GB 2666 Mhz, but in the BIOS Setup, by default, the frequency is
> set
> to "AUTO" (2133 Mhz), and in 2019 I had applied it to 2666 Mhz, and I
> didn't
> remember this.
>
> My friend warned me about this, that what I did was an "overclocking of
> RAM", I
> didn't know that this is an overclocking, so I decided to revert, applying
> "AUTO" again (2133 Mhz).
>
> Since then... the reboots have stopped, however... the system has
> continued to
> freeze, and the logs point only to my NVIDIA GTX 960.
>
> In the BIOS Setup, I disabled the "Global C-State Control", and since
> then, it
> has been almost 60 days since there are no more system freezes or reboots,
> things that happened every day.
>
> Resume:
>
> 1. Maintaining RAM frequency in AUTO resolves reboots;
> 2. Disabling "Global C-State Control" solves my problem with system freezes
> (log points to NVIDIA).
>
> These two things above solved my problem, and that parameter
> "processor.max_cstate = 1" in GRUB is no longer needed.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.