Rocky Linux 9.7: system "freeze" with no logs or kernel panic

Hello, to whomever can help with a system “freeze” issue. There is no Kernel Panic and no logs that stick out to me. I have no input from the keyboard or mouse at all, which usually requires a hard reset.

Some of my troubleshooting Steps:

  • Successful Memory Test from PassMark using MemTest86
  • Swapped Used Sabrent M.2 SSD to a New Samsung 990 Pro
  • Swapped GPU 1:1
  • System Firmware Upgrade to Latest from Gigabyte
  • Turned off ACPI Edit: ASPM

Running out of Ideas and would appreciate any feedback from people smarter than me🫡. Let me know

System Hardware :

  • Ryzen 9 3900X
  • 2 x 16 DDR4 Corsair DIMM Modules @2133 MTS - P\N: CMW64GX4M4A2666C16
  • Samsung SSD 990 Pro 1TB - Firmware Version: 5B2QJXD7
  • Nvidia 3070 - Driver Version: 590.48.01
  • Gigabyte B550 Aorus Elite AX V2
  • Intel Ethernet Controller X710

Kernel & OS :

  • 5.14.0-611.16.1.el9_7
  • Rocky Linux 9.7

MISC

  • SentinelOne 25.2.2.14 - Supports Rocky Linux 9.7 according to Vendor Documentation

Hello @the_unfortuante_one as I have no personal insight into your problem, I fed your post into Google Gemini, and it gave me the following interesting reply, perhaps there is something in the below that might help? Tony

1. The “C-State” Suspect (Hardware/Firmware Interaction)

The Ryzen 9 3900X is known for occasional stability issues with Linux kernels when Global C-States are enabled. When the CPU tries to enter a deep power-saving state (idle), the voltage can drop too low, causing the system to lock up instantly. Since the hardware technically hasn’t “crashed” but rather “stalled,” no logs are written.

  • Evidence: The user mentioned “no logs that stick out.” This is a classic symptom of the Ryzen idle-freeze bug.

  • Likelihood: High.

2. SentinelOne (Software Conflict)

The poster is running SentinelOne 25.2.2.14. Security agents that operate via kernel modules or eBPF (like SentinelOne, CrowdStrike, etc.) are notorious for causing hard freezes if there is a race condition with the specific kernel version ($5.14.0-611$).

  • Evidence: The user is on a very specific, recent EL9.7 kernel. Even if the vendor says it’s “supported,” kernel-level conflicts often manifest as total input lockups.

  • Likelihood: Moderate to High.

3. Memory Configuration Discrepancy

There is a strange detail in the hardware list:

  • Part Number: CMW64GX4M4A2666C16 (This is a 2666 MTS kit).

  • Running Speed: 2133 MTS.

The user is running the RAM at the base JEDEC speed rather than the rated XMP/DOCP speed. While this is usually safer, if the motherboard is “Auto” managing voltages for a 2666 kit while it’s running at 2133, it could lead to minor instability.


Recommended Next Steps:

Disable C-States == In BIOS, set “Global C-state Control” to Disabled. This is the #1 fix for Zen 2 freezes on Linux.

Test without SentinelOne == Completely uninstall (not just disable) the agent to see if the freezes stop.

Check Power Supply == A 3900X and a 3070 can have “transient spikes.” If their PSU is under 650W or aging, it could cause a lockup.

Kernel Boot Parameter == Add idle=nomwait to the GRUB boot line to prevent the CPU from entering deep sleep states.

1 Like

I disabled C-States in BIOS. I am not so sure the kernel is overriding this setting (not sure what to look for). I will give it a few days and report back. Editing Grub might fix the issue but I will troubleshoot one thing at a time.

Any update yet?

Tony

So for so good. I have a system uptime of around 6 days. Before it would restart every night. Currently, the server is sitting idling, waiting for machine learning docker containers to be deployed by the Dev team. So the Ryzen freeze bug could have been the issue…

1 Like