 |
108061922.jpg (166,967 bytes) 1055642847.jpg (143,970 bytes) |
|
|
Can any one tell me the root cause of this issue: which cause this: New cpu or some onboard hardware? |
 |
my best guess is the new CPU. Have you tried with CentOS 8.2? |
 |
I've seen several reports of the new Ryzen 5xxxX chips failing on CentOS 7.9. You will need to report this on bugzilla.redhat.com to get any potential fix and for 7, I'm not sure that's likely to happen. You can try though... or buy an older 3xxx Ryzen instead as they work. |
 |
As @tigalch suggested, you want to install CentOS 8.2, or soon-to-come 8.3. If you need to stay with CentOS 7, give ELRepo's kernel-ml a try. |
|
|
I am having the same issue with the same processor, but with the Gigabyte B500 Aorus Pro AC. I had been running that mobo with a Ryzen 3600X with CentOS 7.x just fine with the F1 BIOS. I upgraded to the F12 BIOS and it still ran fine and I let it run for a day to be reasonably sure. I made sure I was patched up to kernel-3.10.0-1160.21.1.el7.x86_64 before swapping the CPUs and I crashed on the way up with the kernel panic within a second of selecting the kernel to load from the grub menu. I also tried dumbing down the system by deselecting features in BIOS, which had no impact. This included turning off C State support, turbo modes and SVM. I then restored my previous BIOS settings, swapped back to the 3600X and I am back in operation, though not with the CPU upgrade I was looking for. |
 |
psmode: if you must stick with CentOS 7, your best bet is using ElRepo's kernel-ml. RHEL 7 ( and by matter of consequence CentOS 7 ) is in its last stage of maintenance which means that it gets only fixes RH feels that are "important" ( which usually translates in high-risk security issues ) and therefore no new features are backported. The chances of seeing an addition to the kernel to properly support new CPUs are extremely slim. |
- Anonymous
