unexpected thermal throttling

Post Reply
jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

unexpected thermal throttling

Unread post by jobenvil » Mon Jun 11, 2018 3:49 am

Since last week I cannot use the OdroidXU4 anymore, which is reaching the thermal throttling point and therefore shutting down automatically the system. This will be OK if the system load or the temperature would be really high, but this is not the case. At the beginning I thougt that this could be caused be some unattended update, but later on I found out that this was not the case. Since I didn't touch the OdroidXU4 for long time I wonder why suddenly and without any logical reason is failing now.

I monitored the thermal throttling on the serial console:

Code: Select all

root@hiperborea:~# [  510.609001] thermal thermal_zone0: critical temperature reached(236 C),shutting down
The thermal throttling was not really following a logical temperature curve because I was monitoring the CPUs and they showed not such increase of the temperature:

Code: Select all

root@hiperborea:~/tools# uptime
 18:28:39 up 50 min,  1 user,  load average: 0,04, 0,05, 0,05
root@hiperborea:~/tools# ./several_temp_cpus.sh

Every 2,0s:  echo -n 'FREQ CPU 1: ' && cat /sys/dev...  Sun Jun 10 18:28:33 2018

FREQ CPU 1: 200000
FREQ CPU 2: 200000
FREQ CPU 3: 200000
FREQ CPU 4: 200000

FREQ CPU 5: 700000
FREQ CPU 6: 700000
FREQ CPU 7: 700000
FREQ CPU 8: 700000

TEMP CPU 0: 54000
TEMP CPU 1: 51000
TEMP CPU 2: 56000
TEMP CPU 3: 54000

TEMP GPU: 34000

COOLING DEV 0: 0
COOLING DEV 1: 0
COOLING DEV 2: 0

[ 3114.674454] thermal thermal_zone1: critical temperature reached(235 C),shutting down
[ 3114.681243] thermal thermal_zone0: critical temperature reached(236 C),shutting down
[ 3114.697864] thermal thermal_zone1: critical temperature reached(235 C),shutting down
[  OK  ] Stopped tar         Unmounting RPC Pipe File System...
[  OK  ] Stopped Clean PHP session files every 30 mins.
         Stopping User Manager for UID 0...
[  OK  ] Stopped target Sound Card.
[  OK  ] Stopped Daily apt upgrade and clean activities.
I also tested the OdroidXU4 with another new image without any load which corroborates that the temperature was not more than 60 °C. The OdroidXU4 keeps still shutting down. This means that some sensor inside the OdroidXU4 is giving wrong values, probably is damaged and therefore sending the wrong signal to the system. I also removed the fan and the heatsink and controlled the temperature on the Exynos chip manually. Puting on the system on powersave mode and other cpu-freq tunning doesn't help as well.

The OdroidXU4 was working since almost 2,5 years (Invoice HKI1601100146) properly with a Noctua Fan (NOCTUA NF-A4x10 5V) + heatsink. The headless server was used only for seafile-server and the load was really low and sporadically when compiling, the Noctua fan was working really nice not showing in any case a termal shutdown.

My question, how is possible to deactivate the thermal throttling mechanism in order to be able to continue using the OdroidXU4?

Code: Select all

root@hiperborea:~# uname -a
Linux hiperborea 4.9.21-g8abd6e9-dirty #1 SMP PREEMPT Sat Apr 8 20:31:35 CEST 2017 armv7l armv7l armv7l GNU/Linux

User avatar
mad_ady
Posts: 5114
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1
Location: Bucharest, Romania
Contact:

Re: unexpected thermal throttling

Unread post by mad_ady » Mon Jun 11, 2018 4:34 am

Yes, there is a fix to ignore faulty temperature readings, but you need to upgrade to kernel 4.14.

jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

Re: unexpected thermal throttling

Unread post by jobenvil » Mon Jun 11, 2018 5:47 am

This would not be the main problem, but the OdroidXU4 will not pass the compilation process, since sometimes the shutdown appears after less than 20 minutes...
Any idea where I can read more about this fix?

User avatar
rooted
Posts: 6094
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Contact:

Re: unexpected thermal throttling

Unread post by rooted » Mon Jun 11, 2018 11:05 am

mad_ady wrote:Yes, there is a fix to ignore faulty temperature readings, but you need to upgrade to kernel 4.14.
I know about this issue and have seen the fix on github, but what is causing this problem and why are so many having it suddenly?

3.10.y also has this fix enabled

It states a broken TMU but why is this? Is it actually faulty hardware? What are the chances multiple people would have this happen at the same time.
jobenvil wrote: Any idea where I can read more about this fix?
https://github.com/hardkernel/linux/com ... c6e8017f9d

https://github.com/hardkernel/linux/com ... 922d6476f7

4.14.y

https://github.com/hardkernel/linux/blo ... _helpers.c

Same problem here :

https://forum.armbian.com/applications/ ... hed(228-C)
Last edited by rooted on Mon Jun 11, 2018 11:55 am, edited 2 times in total.

User avatar
mad_ady
Posts: 5114
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1
Location: Bucharest, Romania
Contact:

Re: unexpected thermal throttling

Unread post by mad_ady » Mon Jun 11, 2018 11:48 am

You should be able to install the deb package for the kernel without compiling anything.

I think the problem is caused by old age/heat-cooling cycles of the cpu die where the sensor is. Usually such sensors rely on measuring voltage on a transistor (https://www.sensortips.com/featured/get ... ransistor/) and a transient problem can generate a wrong reading.

User avatar
rooted
Posts: 6094
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Contact:

Re: unexpected thermal throttling

Unread post by rooted » Mon Jun 11, 2018 11:58 am

@mad_ady Thanks for the information. I still find it hard to believe multiple people would have this issue at the same time though. I have two XU4 in 24/7 operation, one is quite old and no issue. The XU3 never had this issue that I have seen as well, it's even older.

phaseshifter
Posts: 3014
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: N-1..c1+ ..c-2..xu3 lite,xu4...u-3..
u-2...other odroid acc`s as well
Contact:

Re: unexpected thermal throttling

Unread post by phaseshifter » Mon Jun 11, 2018 3:07 pm

i have 2 things to say..
1: check your thermal compound has it become a cake of dried toast
best thing to remove the hold down pins is a "molex-pin" remover..it fits over those sink hold down`s perfect..
makes easy removal of the sink assy to just check...
2: try reverse power the board..it may not be a total cpu issue..
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

moon.linux
Posts: 1161
Joined: Thu Oct 02, 2014 11:42 pm
languages_spoken: english
Contact:

Re: unexpected thermal throttling

Unread post by moon.linux » Mon Jun 11, 2018 5:53 pm

Actually early thermal sensor registration is broken with latest tmu back port.
Following patch https://patchwork.kernel.org/patch/10396327/ help resolve this issue.

Code: Select all

Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.14.47-132 armv7l)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

0 packages can be updated.
0 updates are security updates.

Last login: Mon Jun 11 02:13:04 2018 from 10.0.0.106
odroid@odroid:~$ dmesg | grep thermal
[    3.677796] thermal thermal_zone0: failed to read out thermal zone (-22)
[    3.683975] thermal thermal_zone1: failed to read out thermal zone (-22)
[    3.690665] thermal thermal_zone2: failed to read out thermal zone (-22)
[    3.697346] thermal thermal_zone3: failed to read out thermal zone (-22)
[    3.704048] thermal thermal_zone4: failed to read out thermal zone (-22)

jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

Re: unexpected thermal throttling

Unread post by jobenvil » Tue Jun 12, 2018 2:06 am

rooted wrote: It states a broken TMU but why is this? Is it actually faulty hardware? What are the chances multiple people would have this happen at the same time.
I suppose yes. Thank you for the links. thumbs up!
phaseshifter wrote:i have 2 things to say..
1: check your thermal compound has it become a cake of dried toast
best thing to remove the hold down pins is a "molex-pin" remover..it fits over those sink hold down`s perfect..
makes easy removal of the sink assy to just check...
2: try reverse power the board..it may not be a total cpu issue..
Indeed, this was my second intuition and I though it was the thermal compound, since I bought a Noctua (+ 40xgold-Heatsinks :D ) on Oct. 2016, could be the reason. Unfortunately the thermal compound was elastic and still sticking in my fingers. I reused the thermal compound from HK with the new heatsink since they were delivered with thermal paste and not possible to use in the OdroidXU4.

Since I bought the new power adapter with 30W 5V/6A on October 2016 as well, I reverted to the Hardkernel one, but exactly the same behavior.

I will order a new one OdroidXU4 and wait until a tested patched 4.14 kernel appears. To have a spare board is not a bad idea :D :D :D

hi, wait, @moon.linux may I download your 4.14.47 kernel?

Code: Select all

Jun  1 13:43:47 hiperborea kernel: [68578.803083] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  1 13:43:47 hiperborea kernel: [68578.816909] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  2 05:14:07 hiperborea kernel: [42770.590203] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  2 05:14:07 hiperborea kernel: [42770.604294] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  2 12:05:23 hiperborea kernel: [ 8338.562630] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  2 12:05:23 hiperborea kernel: [ 8338.572993] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  2 20:25:48 hiperborea kernel: [16969.270237] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  5 20:02:16 hiperborea kernel: [ 2493.070831] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  5 20:02:16 hiperborea kernel: [ 2493.088075] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  6 02:39:01 hiperborea kernel: [14437.860398] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  6 02:39:01 hiperborea kernel: [14437.870509] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  6 02:39:01 hiperborea kernel: [14437.930372] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  6 11:14:43 hiperborea kernel: [12321.602786] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  6 11:14:43 hiperborea kernel: [12321.619344] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  8 17:21:32 hiperborea kernel: [  342.765579] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun  8 17:21:32 hiperborea kernel: [  342.779564] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  8 19:06:03 hiperborea kernel: [ 5894.556807] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun  8 19:06:03 hiperborea kernel: [ 5894.571005] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 11:43:03 hiperborea kernel: [ 4882.190761] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 11:43:03 hiperborea kernel: [ 4882.201394] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 12:35:30 hiperborea kernel: [ 3092.951975] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 12:35:30 hiperborea kernel: [ 3092.958996] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 12:35:30 hiperborea kernel: [ 3092.975646] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 12:35:30 hiperborea kernel: [ 3092.982303] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 14:26:48 hiperborea kernel: [ 4948.864648] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 14:26:48 hiperborea kernel: [ 4948.885146] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 16:04:18 hiperborea kernel: [ 1519.801031] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 16:04:18 hiperborea kernel: [ 1519.807827] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 16:04:18 hiperborea kernel: [ 1519.824765] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 16:04:18 hiperborea kernel: [ 1519.831266] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 16:27:47 hiperborea kernel: [   14.500602] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 16:27:47 hiperborea kernel: [   14.512845] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 18:30:15 hiperborea kernel: [ 3114.674454] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 18:30:15 hiperborea kernel: [ 3114.681243] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 18:30:15 hiperborea kernel: [ 3114.697864] thermal thermal_zone1: critical temperature reached(235 C),shutting down
Jun 10 19:40:16 hiperborea kernel: [  328.902162] thermal thermal_zone0: critical temperature reached(236 C),shutting down
Jun 10 19:40:17 hiperborea kernel: [  328.925681] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 21 01:36:41 hiperborea kernel: [2544787.349006] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 21 01:36:41 hiperborea kernel: [2544787.372431] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 23 00:42:12 hiperborea kernel: [17908.116834] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 23 00:42:12 hiperborea kernel: [17908.127400] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 23 00:42:12 hiperborea kernel: [17908.140361] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 23 00:42:12 hiperborea kernel: [17908.146816] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 23 00:42:12 hiperborea kernel: [17908.154544] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 26 06:18:50 hiperborea kernel: [32457.322599] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 26 20:23:57 hiperborea kernel: [  333.849198] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 26 20:23:57 hiperborea kernel: [  333.886740] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 27 19:39:56 hiperborea kernel: [ 3404.229469] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 27 19:39:56 hiperborea kernel: [ 3404.236279] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 29 20:37:19 hiperborea kernel: [  530.498828] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 29 20:37:19 hiperborea kernel: [  530.518646] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 29 20:37:19 hiperborea kernel: [  530.541810] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 01:09:11 hiperborea kernel: [15394.207535] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 01:09:11 hiperborea kernel: [15394.214453] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 07:16:10 hiperborea kernel: [  650.360960] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 07:16:10 hiperborea kernel: [  650.380052] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.219284] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.226217] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.276702] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.306443] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.336261] thermal thermal_zone1: critical temperature reached(203 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.372002] thermal thermal_zone1: critical temperature reached(203 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.392131] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.410014] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.433900] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.630613] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.648649] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.678423] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.694185] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.724012] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.731459] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.789555] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.807431] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.831384] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.851441] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.932683] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.939439] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.980536] thermal thermal_zone1: critical temperature reached(203 C),shutting down
May 30 21:33:48 hiperborea kernel: [  611.998299] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.012432] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.019515] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.034120] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.041005] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.065542] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:48 hiperborea kernel: [  612.123508] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.167451] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.191264] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.198457] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.213091] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.220162] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 30 21:33:49 hiperborea kernel: [  612.421894] thermal thermal_zone1: critical temperature reached(201 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.748815] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.758231] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.778577] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.800169] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.806797] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.829027] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.839908] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:56 hiperborea kernel: [  408.895613] thermal thermal_zone1: critical temperature reached(203 C),shutting down
May 31 09:23:57 hiperborea kernel: [  409.146077] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:57 hiperborea kernel: [  409.156570] thermal thermal_zone0: critical temperature reached(236 C),shutting down
May 31 09:23:57 hiperborea kernel: [  409.169929] thermal thermal_zone1: critical temperature reached(235 C),shutting down
May 31 09:23:57 hiperborea kernel: [  409.178077] thermal thermal_zone0: critical temperature reached(236 C),shutting down

User avatar
odroid
Site Admin
Posts: 29380
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: unexpected thermal throttling

Unread post by odroid » Tue Jun 12, 2018 3:55 pm

Please try this latest Ubuntu Mate image.
https://wiki.odroid.com/odroid-xu4/os_i ... 4/20180501

If you prefer a minimal headless Ubuntu, try this.
https://wiki.odroid.com/odroid-xu4/os_i ... 4/20180531

jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

Re: unexpected thermal throttling

Unread post by jobenvil » Wed Jun 13, 2018 1:25 am


User avatar
rooted
Posts: 6094
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Contact:

Re: unexpected thermal throttling

Unread post by rooted » Wed Jun 13, 2018 1:30 am

jobenvil wrote:may I use this other one?

http://deb.odroid.in/5422-s/pool/main/l ... _armhf.deb
Should work.

jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

Re: unexpected thermal throttling

Unread post by jobenvil » Wed Jun 13, 2018 3:29 am

that was all folks...

Code: Select all

root@hiperborea ~ # ./powersave
"powersave"
"powersave"
"powersave"
"powersave"
"powersave"
"powersave"
"powersave"
"powersave"
root@hiperborea ~ # dpkg -i --force-all linux-image-4.14.47-132_20180603_armhf.deb
Vormals nicht ausgewähltes Paket linux-image-4.14.47-132 wird gewählt.
(Lese Datenbank ... 115930 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von linux-image-4.14.47-132_20180603_armhf.deb ...

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Session stopped
    - Press <return> to exit tab
    - Press R to restart session
    - Press S to save terminal output to file

Server unexpectedly closed network connection
:evil: :evil: :evil:

User avatar
mad_ady
Posts: 5114
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1
Location: Bucharest, Romania
Contact:

Re: unexpected thermal throttling

Unread post by mad_ady » Wed Jun 13, 2018 4:34 am

I know it looks bad, but you can still recover from that. Connect the emmc/sd to a linux pc, mount both partitions and navigate to part2/var/cache/apt/packages and locate the linux-image package. Use mc to look inside and enter the cpio archive inside. From here you can extract kernel/initrd and place them in part1/, and /lib/modules and place them in part2/lib/modules.
It should reboot with the new kernel.

User avatar
rooted
Posts: 6094
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Contact:

Re: unexpected thermal throttling

Unread post by rooted » Wed Jun 13, 2018 7:00 am

No one said use force all, I would have told you to backup boot first.

jobenvil
Posts: 42
Joined: Tue Feb 09, 2016 7:11 pm
languages_spoken: spanish, english, german
ODROIDs: odroidxu4
Location: Düsseldorf
Contact:

Re: unexpected thermal throttling

Unread post by jobenvil » Fri Jul 06, 2018 2:28 am

I have to face some open points like to expand my old fat32 partition, fushing blobs, etc, -somehow my old self compilated "dirty" u-boot stays there... in the meanwhile I received the new XU4 with passive heatsink in cooles blue color and I could perform further troubleshooting with my old SD_CARD

I installed the odroid 4.14.52-145 kernel version and since one week my old XU4 runs like before. The unexpected shutdown due to broken TMU is patched.

BTW, is this the correct repository for the OdroidXU4?

Code: Select all

deb http://deb.odroid.in/5422-s/ xenial main
Somehow I had to install the new kernel myself (I suppoused this will happen automatically, but was not the case):

Code: Select all

dpkg -i linux-odroid-5422_4.14.52-145_armhf.deb

but firstly removing the linux-image

Code: Select all

apt-get remove linux-image-4.14.47-132
is this the expected correct behaviour or the properly procedure for future kernel updates?

BTW, the new Seafile Server version for ARM was posted today...

markephillips
Posts: 17
Joined: Fri Oct 26, 2018 11:39 am
languages_spoken: english
ODROIDs: xu4
Contact:

Re: unexpected thermal throttling

Unread post by markephillips » Wed Nov 28, 2018 10:15 am

Hi I am seeing this same issue:

[ 3.774600] thermal thermal_zone0: failed to read out thermal zone (-22)
[ 3.780884] thermal thermal_zone1: failed to read out thermal zone (-22)
[ 3.787467] thermal thermal_zone2: failed to read out thermal zone (-22)
[ 3.794140] thermal thermal_zone3: failed to read out thermal zone (-22)
[ 3.800866] thermal thermal_zone4: failed to read out thermal zone (-22)

I am also getting the following errors:

[ 0.000031] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 49
[ 0.152393] CPU4: Spectre v2: incorrect context switching function, system vulnerable
[ 0.172367] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.172374] CPU5: Spectre v2: incorrect context switching function, system vulnerable
[ 0.180681] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.180687] CPU6: Spectre v2: incorrect context switching function, system vulnerable
[ 0.188668] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.188675] CPU7: Spectre v2: incorrect context switching function, system vulnerable
[ 1.061522] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[ 1.062507] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[ 1.062591] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[ 1.062962] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[ 1.063055] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator

[ 2.104811] exynos-hdmi 14530000.hdmi: Failed to get supply 'vdd': -517

[ 2.187683] devfreq devfreq0: Couldn't update frequency transition information.
[ 3.694397] (NULL device *): Direct firmware load for s5p-mfc-v8.fw failed with error -2
[ 3.702700] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[ 4.116258] OF: graph: no port node found in /soc/hdmi@14530000
[ 4.454956] rtc rtc1: invalid alarm value: 1900-1-1 0:0:0

[ 4.598168] samsung-i2s 3830000.i2s: ASoC: Failed to create component debugfs directory
[ 4.605813] samsung-i2s 3830000.i2s: ASoC: Failed to create component debugfs directory
[ 7.194432] sd 0:0:0:1: [sdb] No Caching mode page found
[ 7.194441] sd 0:0:0:1: [sdb] Assuming drive cache: write through


And I am running the latest Ubuntu Mate image downloaded yesterday. And updated boot.ini with the LCD dual head and USB controller updates - none of which is in the cloudshell2 smb or NAS instructions. All I want is a simple NAS and Apple Time Machine to work and no more messing around with adding random configuration file information. Even OMV doesn't work with Cloudshell2 with drives connected.

Help would be greatly appreciated. I just end up copying the errors and searching for xu4 or cloudshell and reading what others have done - the first thermo throlling only had C code kernal updates and I'm just not going to start over again -I'm on my 10th OS rebuild. I just want something stable.

Output of uname -a

Linux Cloudshell2 4.14.81-151 #1 SMP PREEMPT Thu Nov 15 06:10:52 -02 2018 armv7l armv7l armv7l GNU/Linux

Output of lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

User avatar
odroid
Site Admin
Posts: 29380
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: unexpected thermal throttling

Unread post by odroid » Wed Nov 28, 2018 10:25 am

Those error messages in Kernel log is very normal. I can see it too with the same kernel version.

You can monitor 4 big CPUs and GPU temperature with this command.

Code: Select all

odroid@odroid:~$ cat /sys/devices/virtual/thermal/thermal_zone*/temp            
56000                                                                           
59000                                                                           
58000                                                                           
57000                                                                           
57000 
My CPU temperature is around 57~59°C at this moment.

markephillips
Posts: 17
Joined: Fri Oct 26, 2018 11:39 am
languages_spoken: english
ODROIDs: xu4
Contact:

Re: unexpected thermal throttling

Unread post by markephillips » Thu Nov 29, 2018 8:50 am

Thanks. Ok, I feel better. Its been a constant concern getting this cloudshell to be stable - which I think I can say it finally is! cross my fingers and not to jinx it.

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 0 guests