H6 Famous Reboot problem

[haajee]

19 minutes ago, NicoD said:

I usually use blender. But 7zip is ok too. install it : sudo apt install p7zip-full
And to run it : 7z b

Run it a few times right behind each other. It doesn't max out the CPU completely. But even with that I'm getting 95°C after 2 runs.
For blender you download this file and unzip. Install blender, sudo ap install blender. Open Blender and open the cpu file of the downloaded files.
Then click render.
I use a taskbar app to see the temperature. You can use htop or so to do the same. I also wrote a simple program to do the same. As long as you keep an eye on the temp.

Do know that I'm using a dev 5.1 image. The 5.0 images should be throttling normally.

I am running 5.1 to. The room temperature is arround 23 degrees celcius. I have the Orange Pi One Plus H6 in a plastic case. Simple copper heatsink. Test with and without fan.

 

Round 1 with fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:09:44:  720MHz  0.72   3%   1%   0%   0%   1%   0% 26.9°C
18:09:49: 1080MHz  0.66   1%   0%   0%   0%   0%   0% 26.8°C
18:09:54: 1488MHz  0.69  14%   1%   9%   0%   1%   0% 29.6°C
18:10:01: 1488MHz  0.96  72%   1%  70%   0%   0%   0% 41.0°C
18:10:07: 1488MHz  1.28  89%   2%  86%   0%   0%   0% 38.9°C
18:10:14: 1488MHz  1.50  91%   2%  88%   0%   0%   0% 43.0°C
18:10:19: 1488MHz  2.04  83%   1%  81%   0%   0%   0% 39.4°C
18:10:24: 1488MHz  2.27  89%   2%  86%   0%   0%   0% 40.4°C
18:10:30: 1488MHz  2.49  97%   5%  91%   0%   0%   0% 40.9°C
18:10:35: 1488MHz  2.61  91%   1%  89%   0%   0%   0% 38.5°C
18:10:40: 1488MHz  2.73  71%   3%  67%   0%   0%   0% 40.5°C
18:10:46: 1488MHz  2.75  88%   5%  83%   0%   0%   0% 40.9°C
18:11:11:  720MHz  2.93  97%  28%  26%   0%  42%   0% 31.2°C
18:11:16: 1080MHz 12.37   5%   1%   0%   0%   2%   0% 28.8°C
18:11:21:  888MHz 11.38   2%   0%   0%   0%   0%   0% 28.8°C

 

Round 2 with fan
18:11:26:  888MHz 10.47   4%   1%   2%   0%   0%   0% 28.4°C
18:11:31: 1080MHz  9.63   1%   0%   0%   0%   0%   0% 28.4°C
18:11:36:  888MHz  8.86   1%   0%   0%   0%   0%   0% 28.1°C
18:11:41: 1320MHz  8.15   1%   0%   0%   0%   0%   0% 28.0°C
18:11:46: 1488MHz  7.50  15%   1%  12%   0%   1%   0% 30.6°C
18:11:53: 1488MHz  7.22  83%   1%  80%   0%   0%   0% 42.5°C
18:11:58: 1488MHz  6.95  86%   1%  84%   0%   0%   0% 39.7°C
18:12:05: 1488MHz  6.71  93%   1%  91%   0%   0%   0% 43.7°C
18:12:11: 1488MHz  6.50  81%   1%  79%   0%   0%   0% 40.3°C
18:12:16: 1488MHz  6.13  89%   2%  87%   0%   0%   0% 40.7°C
18:12:21: 1488MHz  6.04  95%   2%  92%   0%   0%   0% 39.3°C
18:12:26: 1488MHz  5.88  89%   1%  88%   0%   0%   0% 36.8°C
18:12:31: 1488MHz  5.57  73%   2%  71%   0%   0%   0% 40.7°C
18:12:36: 1488MHz  5.36  86%   2%  83%   0%   0%   0% 40.6°C
18:13:31: 1320MHz 11.18  98%  47%  11%   0%  39%   0% 33.7°C

 

Round 3 with fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:13:36:  720MHz 28.50   3%   0%   1%   0%   1%   0% 29.6°C
18:13:42: 1488MHz 26.30  47%   1%  44%   0%   0%   0% 40.7°C
18:13:47: 1488MHz 24.51  95%   1%  93%   0%   0%   0% 44.4°C
18:13:52: 1488MHz 21.43  82%   2%  78%   0%   0%   0% 42.1°C
18:13:59: 1488MHz 20.04  94%   1%  93%   0%   0%   0% 44.8°C
18:14:04: 1488MHz 18.83  80%   2%  77%   0%   0%   0% 41.5°C
18:14:09: 1488MHz 17.88  90%   2%  87%   0%   0%   0% 41.8°C
18:14:16: 1488MHz 16.85  94%   2%  91%   0%   0%   0% 44.8°C
18:14:22: 1488MHz 15.82  78%   1%  76%   0%   0%   0% 40.6°C
18:14:27: 1488MHz 14.80  85%   2%  81%   0%   0%   0% 41.1°C
18:14:33: 1488MHz 13.06  90%   3%  87%   0%   0%   0% 41.5°C
18:14:40:  888MHz 14.57  91%  20%  37%   0%  32%   0% 31.7°C
18:14:45: 1080MHz 13.41   1%   0%   0%   0%   0%   0% 30.1°C

 

Round 1 without fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:18:33: 1488MHz  1.69  86%   3%  82%   0%   0%   0% 47.6°C
18:18:39: 1488MHz  1.95  95%   1%  93%   0%   0%   0% 52.2°C
18:18:44: 1488MHz  2.25  78%   2%  75%   0%   0%   0% 49.2°C
18:18:51: 1488MHz  2.47  93%   4%  87%   0%   0%   0% 50.7°C
18:18:58: 1488MHz  2.76  95%   3%  91%   0%   0%   0% 54.0°C
18:19:04: 1488MHz  2.94  77%   1%  75%   0%   0%   0% 49.9°C
18:19:09: 1488MHz  3.03  88%   6%  81%   0%   0%   0% 52.1°C
18:19:15: 1488MHz  3.18  96%  11%  84%   0%   0%   0% 52.4°C
18:19:23: 1320MHz  4.37  91%  16%  35%   0%  38%   0% 42.4°C

 

Round 2 without fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:20:24: 1488MHz  1.60  40%   1%  38%   0%   0%   0% 49.9°C
18:20:30: 1488MHz  2.20  94%   1%  92%   0%   0%   0% 55.8°C
18:20:35: 1488MHz  2.34  84%   2%  81%   0%   0%   0% 52.6°C
18:20:41: 1488MHz  2.48  94%   1%  93%   0%   0%   0% 57.0°C
18:20:47: 1488MHz  2.60  79%   2%  77%   0%   0%   0% 53.9°C
18:20:52: 1488MHz  2.71  90%   2%  87%   0%   0%   0% 55.2°C
18:20:58: 1488MHz  2.90  94%   2%  91%   0%   0%   0% 58.6°C
18:21:04: 1488MHz  3.06  80%   1%  78%   0%   0%   0% 54.9°C
18:21:09: 1488MHz  3.13  84%   2%  81%   0%   0%   0% 55.2°C
18:21:14: 1488MHz  3.28  89%   2%  87%   0%   0%   0% 56.1°C
18:21:24:  720MHz  4.14  93%  13%  37%   0%  41%   0% 46.4°C
18:21:30:  720MHz  4.16   1%   0%   0%   0%   0%   0% 43.6°C

 

Round 3 without fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:21:55: 1488MHz  2.98  42%   1%  39%   0%   0%   0% 55.1°C
18:22:01: 1488MHz  3.06  95%   2%  92%   0%   0%   0% 60.0°C
18:22:06: 1488MHz  3.30  82%   2%  79%   0%   0%   0% 56.5°C
18:22:13: 1488MHz  3.20  94%   1%  92%   0%   0%   0% 61.6°C
18:22:18: 1488MHz  3.02  80%   1%  77%   0%   0%   0% 57.3°C
18:22:23: 1488MHz  3.18  89%   2%  86%   0%   0%   0% 58.3°C
18:22:30: 1488MHz  3.40  93%   2%  90%   0%   0%   0% 62.1°C
18:22:36: 1488MHz  3.33  80%   1%  78%   0%   0%   0% 59.1°C
18:22:41: 1488MHz  3.22  85%   2%  82%   0%   0%   0% 58.8°C
18:22:47: 1488MHz  3.20  90%   2%  87%   0%   0%   0% 60.1°C
18:22:54: 1080MHz  3.59  94%  21%  44%   0%  27%   0% 50.4°C
18:22:59:  888MHz  3.70   3%   1%   0%   0%   1%   0% 46.9°C

 

Round 4 without fan
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
18:23:35: 1488MHz  2.54  54%   1%  52%   0%   0%   0% 57.2°C
18:23:40: 1488MHz  2.74  95%   1%  94%   0%   0%   0% 62.0°C
18:23:45: 1488MHz  2.76  81%   2%  78%   0%   0%   0% 59.0°C
18:23:52: 1488MHz  2.86  94%   1%  93%   0%   0%   0% 63.6°C
18:23:57: 1488MHz  2.79  79%   2%  77%   0%   0%   0% 59.6°C
18:24:02: 1488MHz  2.73  90%   2%  87%   0%   0%   0% 61.4°C
18:24:09: 1488MHz  2.75  94%   2%  91%   0%   0%   0% 64.0°C
18:24:15: 1488MHz  2.94  79%   1%  77%   0%   0%   0% 60.7°C
18:24:20: 1488MHz  2.94  84%   1%  82%   0%   0%   0% 61.6°C
18:24:25: 1488MHz  2.87  90%   3%  86%   0%   0%   0% 62.4°C
18:24:33: 1488MHz  3.28  94%  22%  46%   0%  24%   0% 55.4°C
18:24:38: 1080MHz  3.09   7%   1%   2%   0%   2%   0% 48.9°C

[NicoD]

It'z clocked at 1.5Ghz.

[haajee]

yes sinds the last 2 nightly releases that was also my question a few posts above

[NicoD]

26 minutes ago, haajee said:

yes sinds the last 2 nightly releases that was also my question a few posts above

Right, that was why I've build the dev 5.1. It's at 1.8Ghz from boot. All frequencies are available, even 1.64Ghz)
What available frequencies does it show for you? (cpufreq-info)

[haajee]

14 minutes ago, NicoD said:

Right, that was why I've build the dev 5.1. It's at 1.8Ghz from boot. All frequencies are available, even 1.64Ghz)
What available frequencies does it show for you? (cpufreq-info)

 

Welcome to ARMBIAN 5.87.190519 nightly Ubuntu 18.04.2 LTS 5.1.3-sunxi64

 

analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 480 MHz - 1.49 GHz
  available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 480 MHz and 1.49 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 888 MHz (asserted by call to hardware).
  cpufreq stats: 480 MHz:87.91%, 720 MHz:1.92%, 816 MHz:1.00%, 888 MHz:2.43%, 1.08 GHz:1.51%, 1.32 GHz:0.78%, 1.49 GHz:4.45%  (26822)

 

 

[NicoD]

3 minutes ago, haajee said:

  available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz

Very strange. I should be having the same image. Armbian_5.87_Orangepi3_Ubuntu_bionic_dev_5.1.3_desktop build 19/05/19.
I'm using the OPi3 and you the OPi1+.
I'll download the nightly for OPi3 and see if there's a difference with my build and the nightly. Should be both the same.

Could be there's seperate patches done for the OPi1+ that didn't go in 5.1. I expect the same of the OPi3 throttle issue.
I didn't follow the dev of the OPi1+. Only OPi3 and PineH64. So I don't know the differences between OPi1+ and OPi3. But since they both need different images there's going to be important differences. That needed a seperate approach.

[martinayotte]

2 hours ago, NicoD said:

But could as well have been with @martinayotte for the OPi3.

I'm not very familiar with throttling ...

Could be Igor too ...

[NicoD]

9 minutes ago, martinayotte said:

I'm not very familiar with throttling ...

I'm reading everything again. But with so many pages it could takes days before I find it

54 minutes ago, haajee said:

  available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz

I've jus tried Armbian_5.87.190519_Orangepi3_Ubuntu_bionic_dev_5.1.3 that I downloaded from nightly. It's also 1.8Ghz.
Do you know how this was with kernel 5.0 on the OPi1+?

 

[NicoD]

@martinayotte I've just seen another "reboot problem" with the OPi3. Screensaver/sleep had to go on, but instead it rebooted. Simple fix is to disable sleep.
But since a few months the power manager seems to have disappeared from the Armbian Desktop. I need to install one myself. Is there any reason for this? @Igor It's on all Armbian desktop images since a few months that it seems missing.

[martinayotte]

1 hour ago, NicoD said:

Screensaver/sleep had to go on, but instead it rebooted.

From what I know, Sleep/Hibernate works only on Legacy, since it rely on AR100 ARISC co-processor, not yet supported on Mainline.

That is true for all AllWinner SoC, not only H6 ...

For more details, here is http://linux-sunxi.org/AR100

For example, it is well known that Pinebook with Mainline, doing sleep simply returns to normal desktop, without even doing a reboot.

 

[Igor]

9 hours ago, NicoD said:

power manager seems to have disappeared from the Armbian Desktop

It was designed to be present only on some hardware: https://github.com/armbian/build/blob/master/config/sources/sun50iw1.conf#L108 and as Martin explained even there things are not properly working yet.

[NicoD]

Wouldn't it be better to disable screensaver and power manager settings by default?

Without power manager there's no simple way for the user to disable this him/herself.

I've seen this behaviour before where screensaver didn't work because of the sleep mode of the power manager(N2 Mate Desktop). I'll see if this is also the case here.

[haajee]

I just want to say that my OrangePI One Plus runs perfectly with the release candidate! :) Good job all! I have also give a little donate. Hope that could help you all in the future! Thank you.

[haajee]

The OrangePi One Plus just run´s just perfect for a long time! In my opinion it´s stable? Oh on the official download page on https://www.armbian.com/orange-pi-one-plus/´ i read: ´USB3 sometimes doesn’t detect high-speed devices properly´. But thatś with the One Plus not a (big) deal because the One Plus doesn´t have USB3 ports?

[Werner]

This hint does not fit for this particular board, yes.

Though USB3 with H6 SoC is still an issue with other boards. The support is still WIP: http://linux-sunxi.org/Linux_mainlining_effort

[haajee]

Yes i know that it´s just a problem with the other H6 boards.

[Drakes]

Hi all, it's 2021 and this famous reset problem is still a problem with the Allwinner A64. I've made a long article about everything I tried to get a A64 reset to initiate, even low-level register writes, but I'd like to get another set of eyes on this. Maybe I'm missing something obvious?

[lanefu]

6 hours ago, Drakes said:

I've made a long article about everything I tried

OMG that's an understatement.  Impressive article.

Edited March 28, 2021 by lanefu
clarification