CPU can't loading 100% in BurninTest ARM v5.0

[Wilson_ASRI]

Hi PassMark,

I'm testing the BurninTest ARM v5.0 on Nvidia Orin NX.
The CPU loading can't run to 100%.

CPU: Nvidia Orin NX 16GB (8-core Arm® Cortex®-A78AE v8.2 64-bit CPU 2MB L2 + 4MB L3)
OS : Ubuntu 22.04
Kernel : 5.15

[David (PassMark)]

I would assume it is overheating and throttling the cores.



I looked up the spec sheet for you.

[Wilson_ASRI]

Hi David,

I don’t think so. We have conducted numerous tests focusing on temperature and performance.

On the same machine:

• With the previous version, Jetpack 5 (Ubuntu 20.04, Kernel 5.10), all CPUs could consistently run at 100% without any issues.
• However, with the current Jetpack 6 (Ubuntu 22.04, Kernel 5.15), it is no longer possible to achieve 100% on all CPUs.

Even when running BurnInTest right after startup, before the system temperature rises, the CPUs are already unable to reach 100%.

Best regards,
Wilson Lin

[Wilson_ASRI]

Upload the image showing the state before the system reaches its operating temperature for your reference.

[David (PassMark)]

Try running just the CPU test by itself.
Don't run any other 3rd party software (you seem to be in the first screen shot).
Update to the latest version of BurnInTest. Version 5.0 build 1016 at the moment.

As it was working before the OS update, it is also possible the updated OS broke something, like the process to detect the number of available CPUs. So that would be the next thing to check. Was the correct number of CPU cores detected.

[Wilson_ASRI]

I tried version 5.0 build 1016 and run CPU test only.
It looks still can't run to 100%.

[Richard (PassMark)]

The number of test processes to start up is based on the number of cores detected by BurnInTest. Can you provide the output from the Linux lscpu command?

[Wilson_ASRI]

Hi Richard,

Our company has multiple Nvidia Jetson Orin SKUs. Currently, I have the Orin Nano 4GB module in my hand, which features 6 CPU cores.
The lspcu is:

$ lscpu
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 6
On-line CPU(s) list: 0-5
Vendor ID: ARM
Model name: Cortex-A78AE
Model: 1
Thread(s) per core: 1
Core(s) per cluster: 3
Socket(s): -
Cluster(s): 2
Stepping: r0p1
CPU max MHz: 1510.4000
CPU min MHz: 115.2000
BogoMIPS: 62.50
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop as
imddp uscat ilrcpc flagm paca pacg
Caches (sum of all):
L1d: 384 KiB (6 instances)
L1i: 384 KiB (6 instances)
L2: 1.5 MiB (6 instances)
L3: 4 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-5
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Mitigation; CSV2, but not BHB
Srbds: Not affected
Tsx async abort: Not affected

[Richard (PassMark)]

BurnInTest Linux is looking for "Core(s) per socket:" to determine the number of cores and if it unable to determine the number of cores it will default to 1. We'll update BIT Linux for the next release to use the "CPU(s):" value (and possibly "Core(s) per cluster:" & "Cluster(s):" to verify) as an alternative.

[Wilson_ASRI]

Hi Richard,

Thanks a lot. What time is the next release?

[Richard (PassMark)]

Hi Richard,

Thanks a lot. What time is the next release?

Can you give the following debug build a try to see if it loads the CPU better?

<Link Removed>

If not, can you run BurnInTest with debug logging enable "-d" and send in the logs for us to take a look.

[Wilson_ASRI]

The CPUs is only 1 run to 100%.
These are the log files.

[Richard (PassMark)]

Let's try this again...Can you test the following build and send in the logs if issue persists?

https://www.passmark.com/temp/BurnIn....Debug2.tar.gz

[Wilson_ASRI]

Thanks a lot.
The CPUs are running to 100% for all cores on this version.

[Richard (PassMark)]

The CPUs are running to 100% for all cores on this version.

That is great to hear. You can continue to use the debug version until we released the next build to include the fix.