OPTEE_OS Crashes while running xtest 1013 , when enabling it for an arm64 platform with 8 cores.

[nxa27423]

1. Getting the below error while enabling OPTEE_OS in am ARM64(armv8) based platform with 8 cores.

Test ID: 1013
D/TC:0 tee_ta_init_pseudo_ta_session:274 Lookup pseudo TA e13010e0-2ae1-11e5-896a-0002a5d5c51b
*Run test suite D/TC:1 __wq_rpc:40 sleep thread 1 0xfc057770 0
*D/TC:0 load_elf:842 Lookup user TA ELF e13010e0-2ae1-11e5-896a-0002a5d5c51b (Secure Storage TA)
*F/TC:1 plat_prng_add_jitter_entropy:74 plat_prng_add_jitter_entropy: 0x6AAB
*F/TC:0 plat_prng_add_jitter_entropy:74 plat_prng_add_jitter_entropy: 0x08
*E/TC:0 assertion 'l->curr_thread == -1' failed at core/arch/arm/kernel/thread.c:430 <thread_alloc_and_run>
*E/TC:0 assertion '!have_spinlock()' failed at core/arch/arm/include/kernel/spinlock.h:25 <assert_have_no_spinlock>
ith level=0

TE/TC:0 Panic at core/kernel/assert.c:28 <_assert_break>
EE test applicatE/TC:0 Call stack:
ion started withE/TC:0 0x00000000fc00b1e0
device [(null)]E/TC:0 0x00000000fc01642c
E
#############/TC:0 0x00000000fc014f04
E###############/TC:0 0x00000000fc00708c
E###############/TC:0 0x00000000fc008c90
E#########
/TC:0 0x00000000fc023500 Eegression
##/TC:0 0x00000000fc021518
E###############/TC:0 0x00000000fc0221d8
E###############/TC:0 0x00000000fc0202d0
E###############/TC:0 0x00000000fc022a40
E####

regr/TC:0 0x00000000fc0205b8
sEsion_1013 Test/TC:0 0x00000000fc020884
Econcurency with/TC:0 0x00000000fc024aac
Econcurrent TA
/TC:0 0x00000000fc025310
E regression_101/TC:0 0x00000000fc0043ec
E.1 Using small /TC:0 0x00000000fc00360c
oEncurrency TA
/TC:0 0x00000000fc015cc8
E regression_101/TC:0 0x00000000fc011e94
E.1.1 Busy loop /TC:0 0x00000000fc00879c
Eepeat 10000
/TC:0 0x00000000fc002948

2. It is working, when I set No. of CORES as 4.
3. I am using the following commits of optee repos.
   OPTEE_OS Commit :52983c6ccafc142865766435a6f421f8854f2348
   optee_test Commit :c0e8678b55d399956da0bdce5b1f25c49839172c
   optee_client Commit : 2d542f2074223fde918e68efa4a9ff37f927e604

[sahilnxp]

I think there is some memory corruption(may be array overflow) due to "core configuration", because it is working fine with 4 cores.
Is this related to #2437
Any comments @jforissier @jenswi-linaro ??

[github-actions]

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.