Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Critical Temperature Reached, H3 Overheating

Featured Replies

Hi,
I have problems with NanoPi NEO on Allwinner H3 due to sudden sporadic Linux kernel overheating shut down. I'm using the Linux kernel 4.14 on Debian Trixie.
The syslog shows:

Quote

kernel: thermal thermal_zone0: critical temperature reached (103 C), shutting down


The hours before, the kernel shows above 80°C by:

Quote

cat /sys/class/thermal/thermal_zone0/temp



But there is not much load on it. When looking to "top" I see less then 10% as load average and more then 90% idle. "iotop" shows all processes <1%. And when measuring the chips, all are cool at below 40°C

It looks like the CPU suddenly get into a hot-state above 80°C, because it stays there for hours independent from the process load. Even after a reboot command, the system comes up again and is still above unrealistic 80°C even with no load.
A power cycle temporarily fixes the problem. The system comes up with about 50°C and slowly cools down to about 30°C for the next 1 to 3 weeks. Then it suddenly becomes hot again until shutting down.

Any experiences with this, what helps? Is there a kernel patch available?

 Thanks

Solved by going

  • Author

Kernel 4.14 is still part of the image delivered by FriendlyElec with NanoPi NEO.
What you probably want to say: First upgrade to a more recent kernel, maybe this fixes the problem.... 

  • Solution
01.10.2024 в 16:47, Achim Scheidl сказал:

A power cycle temporarily fixes the problem. The system comes up with about 50°C and slowly cools down to about 30°C for the next 1 to 3 weeks. Then it suddenly becomes hot again until shutting down.

This is an old and well-known problem for that time.
The SOC has a controller (ARISC architecture).

The code of that time randomly started the controller at the maximum frequency, for example, when the OS was turned off with the sudo poweroff command.
If you did not pull the plug out of the socket, then the processor chip began to warm up more than when the OS was running.

 

You need to update the u-boot and kernel to the current versions.

  • Author

Wow, this is very important information for me, I will try to fix it with the proposals you made - which will take some time....

Thanks very much für this background info

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.