En cualquier caso, hemos repetido el ensayo utilizando la versión sbc-bench -r como proponen al final.
pi@NanoPi-M6:~$ sudo /bin/bash ./sbc-bench.sh -r
[sudo] contraseña para pi:
Starting to examine hardware/software for review purposes…
Average load and/or CPU utilization too high (too much background activity). Waiting…
Too busy for benchmarking: 20:06:01 up 51 min, 3 users, load average: 0.23, 3.18, 3.05, cpu: 36%
Too busy for benchmarking: 20:06:06 up 51 min, 3 users, load average: 0.21, 3.13, 3.03, cpu: 0%
Too busy for benchmarking: 20:06:11 up 51 min, 3 users, load average: 0.19, 3.07, 3.02, cpu: 0%
Too busy for benchmarking: 20:06:16 up 51 min, 3 users, load average: 0.18, 3.02, 3.00, cpu: 0%
Too busy for benchmarking: 20:06:21 up 51 min, 3 users, load average: 0.16, 2.97, 2.98, cpu: 0%
Too busy for benchmarking: 20:06:26 up 51 min, 3 users, load average: 0.23, 2.94, 2.97, cpu: 0%
Too busy for benchmarking: 20:06:32 up 51 min, 3 users, load average: 0.21, 2.89, 2.96, cpu: 0%
sbc-bench v0.9.68
Installing needed tools: apt-get -f -qq -y install mmc-utils smartmontools stress-ng. Done.
Checking cpufreq OPP. Done.
Executing tinymembench. Done.
Executing RAM latency tester. Done.
Executing OpenSSL benchmark. Done.
Executing 7-zip benchmark. Done.
Throttling test: heating up the device, 5 more minutes to wait. Done.
Checking cpufreq OPP again. Done (20 minutes elapsed).
Results validation:
* Advertised vs. measured max CPU clockspeed: -1.2% before, -1.6% after -> https://tinyurl.com/32w9rr94
* Background activity (%system) OK
* No throttling
Full results uploaded to https://0x0.st/XULe.bin
# FriendlyElec NanoPi M6
Tested with sbc-bench v0.9.68 on Fri, 25 Oct 2024 20:26:38 +0200. Full info: [https://0x0.st/XULe.bin](
### General information:
Information courtesy of cpufetch:
SoC: Rockchip RK3588
Technology: 8nm
CPU 1:
Microarchitecture: Cortex-A55
Max Frequency: 1.800 GHz
Cores: 4 cores
Features: NEON,SHA1,SHA2,AES,CRC32
CPU 2:
Microarchitecture: Cortex-A76
Max Frequency: 2.304 GHz
Cores: 4 cores
Features: NEON,SHA1,SHA2,AES,CRC32
The CPU features 3 clusters consisting of 2 different core types:
Rockchip RK3588S (35881000 / 35 88 12 fe 33 41 32 52 30 42 00 00 00 00), Kernel: aarch64, Userland: arm64
CPU sysfs topology (clusters, cpufreq members, clockspeeds)
cpufreq min max
CPU cluster policy speed speed core type
0 0 0 408 1800 Cortex-A55 / r2p0
1 0 0 408 1800 Cortex-A55 / r2p0
2 0 0 408 1800 Cortex-A55 / r2p0
3 0 0 408 1800 Cortex-A55 / r2p0
4 0 4 408 2304 Cortex-A76 / r4p0
5 0 4 408 2304 Cortex-A76 / r4p0
6 0 6 408 2304 Cortex-A76 / r4p0
7 0 6 408 2304 Cortex-A76 / r4p0
15950 KB available RAM
### Governors/policies (performance vs. idle consumption):
Original governor settings:
cpufreq-policy0: performance / 1800 MHz (conservative ondemand userspace powersave performance schedutil / 408 600 816 1008 1200 1416 1608 1800)
cpufreq-policy4: performance / 2304 MHz (conservative ondemand userspace powersave performance schedutil / 408 600 816 1008 1200 1416 1608 1800 2016 2208 2304)
cpufreq-policy6: performance / 2304 MHz (conservative ondemand userspace powersave performance schedutil / 408 600 816 1008 1200 1416 1608 1800 2016 2208 2304)
dmc: dmc_ondemand / 534 MHz (rknpu_ondemand dmc_ondemand vop2_ondemand userspace powersave performance simple_ondemand / 534 1320 1968 2400)
fb000000.gpu: simple_ondemand / 300 MHz (rknpu_ondemand dmc_ondemand vop2_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)
fdab0000.npu: rknpu_ondemand / 300 MHz (rknpu_ondemand dmc_ondemand vop2_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)
fdd90000.vop: vop2_ondemand / 500 MHz (rknpu_ondemand dmc_ondemand vop2_ondemand userspace powersave performance simple_ondemand / 500 750 850)
Tuned governor settings:
cpufreq-policy0: performance / 1800 MHz
cpufreq-policy4: performance / 2304 MHz
cpufreq-policy6: performance / 2304 MHz
dmc: performance / 2400 MHz
fb000000.gpu: performance / 1000 MHz
fdab0000.npu: performance / 1000 MHz
fdd90000.vop: performance / 850 MHz
Status of performance related policies found below /sys:
/sys/devices/platform/
/sys/module/pcie_aspm/
### Clockspeeds (idle vs. heated up):
Before at 42.5°C:
cpu0-cpu3 (Cortex-A55): OPP: 1800, Measured: 1809
cpu4-cpu5 (Cortex-A76): OPP: 2304, Measured: 2276 (-1.2%)
cpu6-cpu7 (Cortex-A76): OPP: 2304, Measured: 2291
After at 59.2°C:
cpu0-cpu3 (Cortex-A55): OPP: 1800, Measured: 1803
cpu4-cpu5 (Cortex-A76): OPP: 2304, Measured: 2266 (-1.6%)
cpu6-cpu7 (Cortex-A76): OPP: 2304, Measured: 2282
### Performance baseline
* cpu0 (Cortex-A55): memcpy: 5798.2 MB/s, memchr: 2772.7 MB/s, memset: 21946.3 MB/s
* cpu4 (Cortex-A76): memcpy: 12382.4 MB/s, memchr: 14760.9 MB/s, memset: 27586.6 MB/s
* cpu6 (Cortex-A76): memcpy: 12376.7 MB/s, memchr: 14775.4 MB/s, memset: 27631.9 MB/s
* cpu0 (Cortex-A55) 16M latency: 137.6 138.7 133.9 137.9 133.0 139.3 215.7 377.4
* cpu4 (Cortex-A76) 16M latency: 136.5 125.6 135.0 124.4 135.5 126.0 127.0 128.0
* cpu6 (Cortex-A76) 16M latency: 138.6 125.2 136.4 124.5 135.2 124.9 123.0 125.2
* cpu0 (Cortex-A55) 128M latency: 160.2 161.4 159.7 161.4 159.4 160.9 234.2 407.5
* cpu4 (Cortex-A76) 128M latency: 154.3 152.9 153.8 152.6 153.5 152.2 153.2 158.3
* cpu6 (Cortex-A76) 128M latency: 152.7 152.1 152.4 151.9 152.5 151.0 151.0 155.6
* 7-zip MIPS (3 consecutive runs): 15879, 15844, 15881 (15870 avg), single-threaded: 3000
* aes-256-cbc 146060.50k 385735.00k 652195.16k 788456.11k 839371.43k 842902.19k (Cortex-A55)
* aes-256-cbc 549804.71k 977689.75k 1198941.27k 1265877.33k 1293292.89k 1295903.40k (Cortex-A76)
* aes-256-cbc 553701.65k 983251.54k 1207125.50k 1275013.46k 1302074.71k 1304794.45k (Cortex-A76)
### Storage devices:
* 238.5GB «Lexar SSD NM620 256GB» SSD as /dev/nvme0: Speed 5GT/s (downgraded), Width x1 (downgraded), 0% worn out, drive temp: 35°C, ASPM Disabled
* 29.1GB «Definite counterfeit SD» UHS SDR104 SD card as /dev/mmcblk0: date 08/2024, manfid/oemid: 0x0000fe/0x3432, hw/fw rev: 0x2/0x0
* 28.9GB «Foresee A3A551» HS400 Enhanced strobe eMMC 5.1 card as /dev/mmcblk2: date 01/2022, manfid/oemid: 0x0000d6/0x0103, hw/fw rev: 0x0/0x1200000000000000
### Software versions:
* Debian GNU/Linux 12 (bookworm)
* Compiler: /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 / aarch64-linux-gnu
* OpenSSL 3.0.14, built on 4 Jun 2024 (Library: OpenSSL 3.0.14 4 Jun 2024)
* Boot environment: ddr-v1.17-3488111f83, spl-v1.13, bl31-v1.46, bl32-v1.16, uboot-9abd042ed7-08/16/2024
### Kernel info:
* /proc/cmdline: storagemedia=emmc androidboot.storagemedia=emmc androidboot.mode=normal androidboot.dtbo_idx=0 androidboot.verifiedbootstate=
* Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
* Vulnerability Spectre v1: Mitigation; __user pointer sanitization
* Vulnerability Spectre v2: Mitigation; CSV2, BHB
* Kernel 6.1.57 / CONFIG_HZ=300
Kernel 6.1.57 is not latest 6.1.114 LTS that was released on 2024-10-22.
See https://endoflife.date/linux for details. It is somewhat likely that
a lot of exploitable vulnerabilities exist for this kernel as well as many
unfixed bugs.
But this version string doesn’t matter since this is not an official LTS Linux
from kernel.org. This device runs a Rockchip vendor/BSP kernel.
This kernel is based on a mixture of Android GKI and other sources. Also some
community attempts to do version string cosmetics might have happened, see
https://tinyurl.com/2p8fuubd for example. To examine how far away this 6.1.57
is from an official LTS of same version someone would have to reapply Rockchip’s
thousands of patches to a clean 6.1.57 LTS.
All known settings adjusted for performance. Device now ready for benchmarking.
Once finished stop with [ctrl]- to get info about throttling, frequency cap
and too high background activity all potentially invalidating benchmark scores.
All changes with storage and PCIe devices as well as suspicious dmesg contents
will be reported too.
Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
20:26:39: 1800/2304/2304MHz 6.00 39% 0% 38% 0% 0% 0% 48.1°C
20:27:39: 1800/2304/2304MHz 2.20 0% 0% 0% 0% 0% 0% 44.4°C
20:28:39: 1800/2304/2304MHz 0.81 0% 0% 0% 0% 0% 0% 43.5°C
20:29:39: 1800/2304/2304MHz 0.29 0% 0% 0% 0% 0% 0% 43.5°C
20:30:39: 1800/2304/2304MHz 0.13 0% 0% 0% 0% 0% 0% 42.5°C
20:31:39: 1800/2304/2304MHz 0.05 0% 0% 0% 0% 0% 0% 42.5°C
20:32:39: 1800/2304/2304MHz 0.02 0% 0% 0% 0% 0% 0% 41.6°C
20:33:40: 1800/2304/2304MHz 0.00 0% 0% 0% 0% 0% 0% 41.6°C
20:34:40: 1800/2304/2304MHz 0.08 0% 0% 0% 0% 0% 0% 41.6°C
^C
Cleaning up. Done.
Checking cpufreq OPP again. Done.
Clockspeeds now at 43.5°C:
cpu0-cpu3 (Cortex-A55): OPP: 1800, Measured: 1808
cpu4-cpu5 (Cortex-A76): OPP: 2304, Measured: 2275 (-1.3%)
cpu6-cpu7 (Cortex-A76): OPP: 2304, Measured: 2290
ATTENTION: status of storage devices has changed:
2d1
< * 29.1GB «Definite counterfeit SD» UHS SDR104 SD card as /dev/mmcblk0: date 08/2024, manfid/oemid: 0x0000fe/0x3432, hw/fw rev: 0x2/0x0
Results validation:
* Advertised vs. measured max CPU clockspeed: -1.2% before, -1.6% after -> https://tinyurl.com/32w9rr94
* Background activity (%system) OK
* No throttling
Se confirma que no hay problema alguno en la temperatura del procesador que en ningún caso llega ni a los 50ºC en las pruebas lo que es francamente admirable.
4183