Taichi X370 with Ubuntu idle lock ups/idle freeze

Hi MisterJ !

Sorry for the late response. Ive been waiting to make sure first before i posted my long term results.

So i can safely agree with Kirurgs that the segfault CPU issue has NOTHING to do with the random reboots or system freezes.

Although my CPU is definitely one of the first ones that was affected by the segfault bug, i wont be RMA'ing it. because its not worth my trouble and time. i think i might be able to live with it for now.

On another note, the system instability random reboots or freezes has finally stopped.
What i did was:
1. i reset the BIOS to defaults after having played around with over-clocks.
2. I disabled all C-states and Global C-States.
3. I disabled Cool n' Quiet
4. BIOS version 3.10 is the one i am using, even though 3.20 came out on 13 September (im too scared to upgrade)
5. Ubuntu Kernel 4.4.0-96  (was also stable on 4.4.0-93)

Right now, my system is stable and hasn't been freezing or rebooting.  I have a strong feeling the f**king Global C-States was the cause.

If i come across any other unexpected problem il be sure to update this post. Till then, thanks for your guidance!

HxwRXP, are you still without a solution?  I have not kept up with your thread.  I cannot answer questions you have about Linux and Ryzen.  I do know that the Linux kernel has been modified for new AMD processors.  Please be sure you have the latest.  I also know that AMD was required to release a HW change (processor, I think) for the segfault problem.  I strongly recommend that you open a AMD support ticket and have a discussion with them.  It seems like AMD is making the updated HW available rather sparingly.  Good luck and please keep us informed here.  Thanks enjoy, John.

Hi Kirurgs,

Thanks for your tips.
I have further tried a few things..
1. I have done a memtest86 and only waited for 5 and a half hours which reached about 50% with no errors so i stopped it.
2. I missed the setting to disable "Global C-States" previously, so i went ahead and disabled that as well.  But i havent tested leaving the PC to idle in Ubuntu after that but i will do that today.
3. I decided to overclock the system from BIOS using Pstate settings:
Pstate0 - 98 - 8 - 20  (3800MHz, 1.35v)
Pstate1 - 98 - 8 - 20  (3800MHz, 1.35v)
Pstate2 - i left on default values.
Pstate3 onwards i disabled.

This eventually worked, but what i had to do was Disable global C-States first then power cycle the PC and then edit the Pstate values.
I then installed a fresh Win10 installation, of which i checked the Cinebench score to see also if my system is stable. So the result was good with 1600cn score. and it finished successfully. i checked in hardware monitor that the system was overclocked at 3800MHz from default 3600MHz.

I went back into Ubuntu and i was working fine for 2 or 3 hours. I then decided to restart so that i can just view something in BIOS and as i was there viewing the hdware monitor. Suddenly the PC switches off while I was in BIOS.  Now i dont know why that happened, because i didnt change anything. Everything was working well at 3800MHz.  I tried switching it back on but when it reached BIOS, it switched off again. This happened a few times. So i eventually resetted the BIOS from the CMOS button.

I tried to redo all the values to 3800MHz and after a power cycle reaching the BIOS the PC kept switching off. Like it was overheating or something? im not sure why before it worked and now i cant even overclock.
It seems as if the Fans work over-time in BIOS but my H100i V2 is maybe not increasing its power when in BIOS?

My temps in BIOS the CPU shows always 70-75 degrees Celcius range.
However in Windows the HDW Monitor showed 40 degrees on idle. They dont fluctuate too much. Only when doing Cinebench did it go to 60 or 70 degrees in HDW Monitor.

Anyway, I dont really mind if overclocking doesnt work - i just want a stable system, but i just wanted to tell you what i did so you can maybe have an idea.
if you can please explain to me where exactly i need to change the voltage so that i can do what you did to have a stable system, id really appreciate that.  Im a bit of a noob in overclocking so im not sure exactly which values i need to change.  Where is the SOC? is that the Vcore? or VDD SoC ?

My ram values i did not change at all. i left it at default. I think you only need to change VDD SoC if you change RAM values.

Also, i did another test, I used the kill-ryzen script to check if my CPU is affected by the segfault problem.
I left it for about half an hour and i did get segfaults in bash. So does this mean im one of those users that are genuinely affected by this problem?
Also and most importantly, does the segfault problem have anything to do with my PC randomly switching off or freezing while idling for about 6 hours in Ubuntu?  Because i believe you said you had the same issue.

Thanks in advance for your help

Hi @Kirurgs,

Thank you for your input!  Actually my problem is still not solved. I continue to have the freezes and YES you are right, my PC also randomly reboots every day if i have had my PC on idle OR. .like the other day i was busy simply browsing, hardly using any CPU and my PC just decided to reboot.

Im so upset about this because i have paid so much money on these parts. I really hope i find the solution.

So far i have tried disabling SMT and UEFI in the BIOS, and i had another freeze today.
I have also tried disabling screen lock like you said and i got another freeze.

I havent tested the RAM yet. but when i was downloading the blockchain, it did it so quick that i didnt have a problem with RAM neither did the PC reboot under load.  The many times i have experienced the random reboots, my PC has always been on idle.  However i have NOT seen any error messages in any logs.  The mcelog is not supported by AMD.  I get this error:

mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor.  Please use the edac_mce_amd module instead.  So i dont know what to use to see mce errors.. any idea?

I have a feeling it could be the voltage like you did. I need to try that out and overclock my CPU and RAM.

What motherboard do you have?
Were you getting error message anywhere?

I have few times seen on the Dr. Debug display that the error is 00, which means i must reseat the CPU, thats what the mobo manual says.

HxwRXP, thanks for the update.  I have advised several W10 users not to do what you have done.  I know almost nothing about Linux, but using an OS from Intel on an AMD platform is asking for problems just as you have assumed.  I know Windows does install code specific to the processor.  A fresh OS install should always be done on a new system even if the OS and processor are not changing.  Thanks and enjoy, John.