extended instructions(NEON) get stuck

[arvin]

HI Sir
I ran pt_linux_arm32 for performance testing, chose Processes--1, iterations--1, duration--1 as following pictures shows, few questions
--how long time will be taking for running for extended instructions? I kept it running over night still shows running progressing.
--is there any way to skip the process?
--or any further configuration needed for running?
thanks.

[Richard (PassMark)]

The Short test duration is around 3 seconds per CPU test. Something is not right, the Extended Instructions should NOT be running indefinitely. It is likely stuck in a loop waiting for the test to finish or the test may of exited prematurely (or never started).

Can you let us know the device and system specs you are testing on?

[arvin]

Thanks Richard,

device is a Smartserver which running system information as below:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.7 LTS
Release: 16.04
Codename: xenial
thanks.

[David.K (Passmark)]

Can you open a terminal and run "cat /proc/cpuinfo" and copy/paste the output here.

[arvin]

cat /proc/cpuinfo:

processor : 0
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 6.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10

processor : 1
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 6.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10

Hardware : Freescale i.MX6 Quad/DualLite (Device Tree)
Revision : 0000

Serial :
Board Serial :
SOM Serial :
i.MX6 Serial :

Part :
Model :
Board Revision :
SOM Board Rev. :

WLAN Address :
BT Address :

Software Version:

[David.K (Passmark)]

Could you try running it again with this debug build and uploading the "debug.log" file it creates.

If the program runs more than 5 minutes don't bother running it any longer just close it and send the debug.log file.

[arvin]

Progress currently, the NEON process went through. debug.log attached.

the CPU Mark show incomplete. any reason or should keep it running longer? thanks.

[David.K (Passmark)]

Can you run this build with only 1 test process "-p 1" and upload the debug.log file.

[arvin]

Did test with process "-p 1" and upload the debug.log file accordingly, thanks.

[David.K (Passmark)]

That debug.log looks like it is from the first build.

It might not have been clear but I meant using the second build from my last reply.

The program should be called "pt_linux_arm32_debug10.1.1003.2"

[arvin]

Attached log with "pt_linux_arm32_debug10.1.1003.2" fyi, thanks.

[David.K (Passmark)]

Can you test this new build "pt_linux_arm32_debug10.1.1004.1", again with "-p 1"

If it works with "-p 1" (i.e. the score for SIMD test is > 0) could you also try running it without any command line arguments and upload the "debug.log" file either way.

Thanks.

[arvin]

Did testing for "pt_linux_arm32_debug10.1.1004.1" with “-p 1” and normal, both debug.log uploaded fyi, thanks.

[arvin]

Does Memory Mark include both flash and RAM performance?

[David.K (Passmark)]

Memory Mark is only testing the RAM.
Disk Mark tests the storage, but that test suite is not available on linux.

This is turning out to be a tricky problem to track down.

Could you download and run this build (simd_arm32_10.1.1004.2), it's the SIMD test only with additional debug info.

It should run in < 10 seconds, if it takes any longer press Ctrl + C to exit the program.

It will create a debug file called "simd_debug.log"