Jump to content
  • 0

Orange Pi Plus 2E wrong temperature leads to shutdown


Stinky
 Share

Question

Hi

I trying to return in work OPi+2e board but faced some odd thing.

 

When I trying to boot Armbian I getting temperatures about 180C which leads to shutdown during booting. It reproduceable with all versions from
hirsute/5.12.15 back to oldest avaliable bionic/5.4.8
Official Ubuntu xenial/5.3.5 works fine, but /sys/class/thermal/thermal_zone0/temp gives negative readings (like about -76500)
Installed on eMMC old RetrOrangePi which is Armbian jessie/3.4.113 also works but gives zero (exactly 0) temp reading.
Finger test gives "room temperature" reading and "warm" while old OS works. Definetly not 180C

 

Board itself is from 2017, worked as media player with active cooling so I doubt it was overheated but will not be surprised if it's hardware degradation issue.

Anyway, any ideas how to get it working with current Armbian?
Personaly I'm fine with wrong temp reading if board works. Tried to add thermal.nocrt=1 with no success, probally did something wrong.


buster / 5.10.34 boot log

Скрытый текст

U-Boot SPL 2021.04-armbian (May 06 2021 - 18:38:02 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2021.04-armbian (May 06 2021 - 18:38:02 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus 2E
DRAM:  2 GiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 2 ms (1.9 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 2 ms (74.2 KiB/s)
11528063 bytes read in 570 ms (19.3 MiB/s)
7973464 bytes read in 394 ms (19.3 MiB/s)
Found mainline kernel configuration
33211 bytes read in 9 ms (3.5 MiB/s)
4185 bytes read in 6 ms (680.7 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11527999 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49501000, end 49fff73f ... OK
   Loading Device Tree to 49490000, end 49500fff ... OK

Starting kernel ...

[    7.439733] thermal thermal_zone0: critical temperature reached (182 C), shutting down
[    7.595396] lima 1c40000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
[    7.689589] thermal thermal_zone0: critical temperature reached (180 C), shutting down
[    7.941771] thermal thermal_zone0: critical temperature reached (179 C), shutting down
[    8.189304] thermal thermal_zone0: critical temperature reached (180 C), shutting down
[    8.439176] thermal thermal_zone0: critical temperature reached (179 C), shutting down
[    8.688999] thermal thermal_zone0: critical temperature reached (178 C), shutting down
[    8.938905] thermal thermal_zone0: critical temperature reached (179 C), shutting down
[    9.188769] thermal thermal_zone0: critical temperature reached (179 C), shutting down
[    9.438796] thermal thermal_zone0: critical temperature reached (178 C), shutting down
[    9.688452] thermal thermal_zone0: critical temperature reached (178 C), shutting down
[    9.819537] systemd-journald[510]: Failed to send READY=1 notification message: Connection refused
[    9.833427] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.847882] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.861375] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.876053] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.888726] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.902411] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.918041] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.934278] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.944972] thermal thermal_zone0: critical temperature reached (178 C), shutting down
[    9.957662] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.971624] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.984616] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[    9.998474] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.010293] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.023847] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.035556] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.048623] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.060285] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.073404] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.085168] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.098166] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.109921] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.124611] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.137478] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.149215] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.162283] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.174145] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.187365] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.188106] thermal thermal_zone0: critical temperature reached (179 C), shutting down
[   10.201322] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.219065] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.230966] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.243761] systemd-journald[510]: Failed to send READY=1 notification message: Transport endpoint is not connected
[   10.402700] dwmac-sun8i 1c30000.ethernet: Shutting down
[   10.410562] reboot: System halted

 

Board: Not on the list
Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0

First try latest edge build. Our test board is just fine:

 

  ___  ____  _         ____  _____ 
 / _ \|  _ \(_)  _    |___ \| ____|
| | | | |_) | |_| |_    __) |  _|  
| |_| |  __/| |_   _|  / __/| |___ 
 \___/|_|   |_| |_|   |_____|_____|
                                   
Welcome to Armbian 21.08.0-trunk.32 Focal with bleeding edge Linux 5.12.15-sunxi

No end-user support: untested automated build

System load:   2%           	Up time:       1 day 18:21	
Memory usage:  4% of 1.97G  	IP:	       10.0.30.112
CPU temp:      86°C           	Usage of /:    9% of 15G    	

[ General system configuration (beta): armbian-config ]

Last login: Sat Jul 17 00:42:50 2021 from 10.0.10.8
root@orangepiplus2e:~# cat /sys/class/thermal/thermal_zone0/temp
79189

 

... but since you said you tried 5.12.y and all others is seems something we can't help much. Custom mitigation to ignore sensor values?

Link to comment
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

  • 0
17.07.2021 в 16:44, Igor сказал:

Custom mitigation to ignore sensor values?

Yeah, I thought about something like that, but can't figure out where dig to.
Is there shorter way than recompiling kernel with disabled thermal?

Link to comment
Share on other sites

  • 0

Well, it's lame but works for me.

 

First I compiled kernel without sun8i_thermal module and placed it on SD. System booted, temp readings like -78000.
Ended up with blacklisting that module so I can use stock kernels with same result.
 

 

Link to comment
Share on other sites

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
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...