ASRock Forums : X399 Taichi CPU Temperature

X399 Taichi CPU Temperature : Tctl is what temperature the CPU...

Sun, 17 Dec 2017 12:33:49 +0000

Author: ssateneth
Subject: 6912
Posted: 17 Dec 2017 at 12:33pm

Tctl is what temperature the CPU itself reports. No chipset, no 3rd party chip. It's been detected that Tctl is 27C higher than actual for threadripper. So if it shows 70C on idle, you are really only at 43C. Ryzen 1800x, 1700x, 1600X etc show similar behavior. Their difference is 17C. Non-X ryzen shows real temperature for Tctl. The purpose for 'wrong' temperature is for tuning boost speeds/voltages and fan speed curve more correctly since threadripper and X-series ryzen have higher TDP and can consume more power and in turn put out more heat.

X399 Taichi CPU Temperature : I just briefly googled, and here...

Sat, 16 Dec 2017 23:05:25 +0000

Author: jmmec
Subject: 6912
Posted: 16 Dec 2017 at 11:05pm

I just briefly googled, and here is a summary from different sources with some tweaks for clarity:

Tdie is the temperature on the die, so that's the one you want to concentrate on.

Tctl is the control temperature, which is what gets reported to your cooling system. The +27C offset is to get it to kick in sooner (it's only for the X versions).

Regarding Tctl on Threadripper it has an offset of 27 degrees. So a reported temperature of 90 degrees (by most programs that don't also offer Tdie) would actually mean a Tdie of 63 degrees on Threadripper.

For example, if I turn on DrDebug to have it report temps when booted into an OS, then this is what I get:

DrDebug = 44 (this is the Tctl temp)

And this is what my OS reports (ArchLinux):

SYSTIN:                 +17.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPUTIN:                 +17.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN0:                 +6.0°C    sensor = thermistor
AUXTIN1:                +18.0°C    sensor = thermistor
AUXTIN2:                +18.0°C    sensor = thermistor
AUXTIN3:                +19.0°C    sensor = thermistor
SMBUSMASTER 0:          +44.5°C

So:

1. My CPU is really operating at 17 (Tdie), and not the higher temp reported by DrDebug (Tctl).

2. I have a 27C offset as expected: 44 (Tctl) - 17 (Tdie) = 27

3. It looks like SMBUSMASTER == Tctl, but with better resolution than DrDebug can display.

X399 Taichi CPU Temperature : Excellent!Thanks again for following...

Wed, 13 Dec 2017 16:25:24 +0000

Author: underthedog
Subject: 6912
Posted: 13 Dec 2017 at 4:25pm

Excellent!
Thanks again for following up and for linking your post to this one. That way, hopefully, it can serve to help others.

X399 Taichi CPU Temperature : I have the same issue (that doesn't...

Wed, 13 Dec 2017 15:09:03 +0000

Author: Freakazoidx86
Subject: 6912
Posted: 13 Dec 2017 at 3:09pm

I have the same issue (that doesn't really seems to affect me in anyway though), I made this post too, looking to know if It was just me or something global across m4 motherboards.

But as I mentioned in my post, I didn't have this bad temp reading in BIOS version 3.30

My post:
http://forum.asrock.com/forum_posts.asp%3FTID=6827&title=ab350-pro4-bios-v330-cpu-temp-offset

X399 Taichi CPU Temperature : Thank you so much for replying.The...

Wed, 13 Dec 2017 11:26:36 +0000

Author: underthedog
Subject: 6912
Posted: 13 Dec 2017 at 11:26am

Thank you so much for replying.
The only thing that's still of concern for me, though, is when I set the "Dr. Debug" display on the Motherboard to show CPU Temperature, the Temperature shown there is 60-70 degrees as well, throughout the time that I'm within the Operating System. Do you think that can be ignored for the same reasons you mentioned before?

Edited by underthedog - 13 Dec 2017 at 11:51am

X399 Taichi CPU Temperature : Hey,I have a similar setup as...

Wed, 13 Dec 2017 10:02:58 +0000

Author: jmmec
Subject: 6912
Posted: 13 Dec 2017 at 10:02am

Hey,

I have a similar setup as you: X399 / Threadripper with ArchLinux, but I also dual boot Windows 10.

In UEFI there is no real OS running to throttle / idle the CPU, so it is pretty much running full blast (at least 1+ cores) which of course raises your temps. So what you experience in UEFI is normal and expected.

X399 Taichi CPU Temperature : Well, adding images to this forum...

Tue, 12 Dec 2017 12:49:01 +0000

Author: underthedog
Subject: 6912
Posted: 12 Dec 2017 at 12:49pm

Well, adding images to this forum is a pain.

https://plus.google.com/photos/photo/106231773890788527158/6498522388202353698

Edited by underthedog - 12 Dec 2017 at 1:10pm

X399 Taichi CPU Temperature : Based on other discussions, such...

Tue, 12 Dec 2017 12:13:07 +0000

Author: underthedog
Subject: 6912
Posted: 12 Dec 2017 at 12:13pm

Based on other discussions, such as this one on reddit

CPUTIN is the socket temp (motherboard thermistor) and SYSTIN is the thermistor on the chipset. I forgot which AUXTIN1/2 is the vrm but there are a few on it. SMBUS is a digital reported CPU temperature which includes the offset, so you need to -27C for the 1950x and whatever the 1920x offset is.

I'm not sure why AMD CPUs or the Motherboard (?) doesn't adhere to existing standards; or, why the temperature input wouldn't be listed within sysfs.

X399 Taichi CPU Temperature : I wonder if anyone knows or has...

Tue, 12 Dec 2017 12:08:19 +0000

Author: underthedog
Subject: 6912
Posted: 12 Dec 2017 at 12:08pm

I wonder if anyone knows or has a guess why the UEFI for the X399 Taichi motherboard displays CPU temperature at high levels 60-70 degrees, while OS software sensors show nothing as high as that.
I use ArchLinux; the sysfs filesystem, which is used for hardware device-specific items, only shows:


nct6779-isa-0290
Adapter: ISA adapter
Vcore:                  +0.71 V  (min =  +0.00 V, max =  +1.74 V)
in1:                    +1.09 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                   +3.33 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                  +3.33 V  (min =  +2.98 V, max =  +3.63 V)
in4:                    +1.86 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +0.91 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +1.21 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                   +3.47 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                   +3.28 V  (min =  +2.70 V, max =  +3.63 V)
in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in10:                   +0.87 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                   +0.90 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                   +0.91 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +0.94 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                  1134 RPM  (min =    0 RPM)
fan2:                  1450 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                  1157 RPM  (min =    0 RPM)
fan5:                  1120 RPM  (min =    0 RPM)
SYSTIN:                 +28.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:                 +30.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                +15.0°C    sensor = thermistor
AUXTIN1:                +33.0°C    sensor = thermistor
AUXTIN2:                +31.0°C    sensor = thermistor
AUXTIN3:                +29.0°C    sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

amdgpu-pci-4200
Adapter: PCI adapter
fan1:          25 RPM
temp1:        +33.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

iwlwifi-virtual-0
Adapter: Virtual device
temp1:            N/A