Odroid XU4 temperature 95°C

djkobi97 · 17 September 2017 19:52

Hello,

i use my Odroid XU4 for plex transcoding and when i transcode the temperature goes up to 95°C is this normal ?
If i use the command cpu it says that the cpu can be damaged, is this true ? i googled it and some of them say that 95°C is normal.
Now i underclock my cpu and the temperature is fine but i would like to use the normal clock.

k-plan · 17 September 2017 20:00

djkobi97 · 17 September 2017 20:08

but why is there a warning from dietpi that this temperature can harm my device ?

k-plan · 17 September 2017 20:14

It is a general setting for ALL supported devices:

github.com

Fourdee/DietPi/blob/master/dietpi/dietpi-cpuinfo#L155


      
          #!/bin/bash
          {
          	#////////////////////////////////////
          	# DietPi CPU Info Script
          	#
          	#////////////////////////////////////
          	# Created by Daniel Knight / daniel.knight@dietpi.com / dietpi.com
          	#
          	#////////////////////////////////////
          	#
          	# Info:
          	# - Location: /boot/dietpi/dietpi-cpuinfo
          	# - Prints CPU information
          	#
          	# Usage:
          	# - /boot/dietpi/dietpi-cpuinfo
          	#////////////////////////////////////
          
          	# Import DietPi-Globals --------------------------------------------------------------
          	. /boot/dietpi/func/dietpi-globals
          	readonly G_PROGRAM_NAME='DietPi-CPU_info'
          	G_INIT
          	# Import DietPi-Globals --------------------------------------------------------------
          
          	aCPU_CUR_FREQ=()
          	aCPU_MIN_FREQ=()
          	aCPU_MAX_FREQ=()
          	Obtain_Cpu_Freq()
          	{
          		for ((i=0; i<$G_HW_CPU_CORES; i++))
          		do
          			[[ -f /sys/devices/system/cpu/cpu$i/cpufreq/scaling_cur_freq ]] && read -r aCPU_CUR_FREQ["$i"] < "/sys/devices/system/cpu/cpu$i/cpufreq/scaling_cur_freq"
          			[[ -f /sys/devices/system/cpu/cpu$i/cpufreq/scaling_min_freq ]] && read -r aCPU_MIN_FREQ["$i"] < "/sys/devices/system/cpu/cpu$i/cpufreq/scaling_min_freq"
          			[[ -f /sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq ]] && read -r aCPU_MAX_FREQ["$i"] < "/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq"
          		done
          	}
          
          	CPU_TEMP_PRINT=
          	Obtain_Cpu_Temp(){ CPU_TEMP_PRINT=$(print_full_info=1 G_OBTAIN_CPU_TEMP); }
          
          	CPU_GOV_CURRENT='N/A'
          	Obtain_Cpu_Gov(){ [[ -f '/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor' ]] && read -r CPU_GOV_CURRENT < /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor; }
          
          	Print_Stats()
          	{
          		echo -e "\n \e[38;5;154m─────────────────────────────────────────────────────\e[0m\n \e[1mDietPi CPU Info\n\e[90m Use dietpi-config to change CPU / performance options\e[0m\n \e[38;5;154m─────────────────────────────────────────────────────\e[0m"
          
          		(( $G_HW_MODEL == 20 )) && echo -e '\n\e[90m[\e[93mWARNING\e[90m] \e[97mMost CPU info is not available on virtual machines.\e[0m\n'
          
          		echo -e " Architecture \e[90m|\e[0m     $G_HW_ARCH_NAME
           Temperature  \e[90m|\e[0m     $CPU_TEMP_PRINT
           Governor     \e[90m|\e[0m     $CPU_GOV_CURRENT"
          
          		if [[ $CPU_GOV_CURRENT == 'ondemand' || $CPU_GOV_CURRENT == 'conservative' ]]
          		then
          			echo -e " Throttle up  \e[90m|\e[0m     $(sed -n '/^[[:blank:]]*CONFIG_CPU_USAGE_THROTTLE_UP=/{s/^[^=]*=//p;q}' /boot/dietpi.txt)% CPU usage"
          		fi
          
          		# CPU freq table: Print only if any content
          		(( ${#aCPU_CUR_FREQ[@]} )) || return 0
          		echo -e '\n \e[90m                Current Freq    Min Freq   Max Freq\e[0m'
          		for i in "${!aCPU_CUR_FREQ[@]}"
          		do
          			echo -e " \e[90mCPU$i         |\e[0m      $(( ${aCPU_CUR_FREQ[$i]:-0} / 1000 )) MHz      \e[90m$(( ${aCPU_MIN_FREQ[$i]:-0} / 1000 )) MHz    $(( ${aCPU_MAX_FREQ[$i]:-0} / 1000 )) MHz\e[0m"
          		done
          		echo
          		G_DIETPI-NOTIFY 2 'The current CPU frequency may be affected by processing this script itself.\n'
          	}
          
          	#/////////////////////////////////////////////////////////////////////////////////////
          	# Main Loop
          	#/////////////////////////////////////////////////////////////////////////////////////
          	Obtain_Cpu_Freq
          	Obtain_Cpu_Temp
          	Obtain_Cpu_Gov
          
          	Print_Stats
          
          	#-----------------------------------------------------------------------------------
          	exit 0
          	#-----------------------------------------------------------------------------------
          }

If you know what are you doing and don’t like it, edit it or ignore it or don’t use it …

Fourdee · 18 September 2017 15:51

Could also improve the cooling solution to achieve full clocks for longer than 3 seconds:

95’c is far too hot for sustained usage. The SoC lifespan will be reduced and most likely fail within a month or two. The other issue is heat dissipation from the SoC to the PCB, yet again increasing the heat of all components on the board. Rinse repeat.

You wouldn’t red-line your car constantly for a 24 hour period (vs normal driving), then expect the engine to have the same life span afterwards, let alone work.

Redline:
drive with (a car engine) at or above its rated maximum revolutions per minute.