Comment 3 for bug 2017650

This issue can be found on node rizzo with M-6.5.0-42.42 as well (with LTP latest upstream)

Here are some debug information on rizzo (SMT is activated):
$ cat /sys/devices/system/cpu/smt/active
1
$ sudo dmidecode -t processor|grep Count
 Core Count: 4
 Thread Count: 8

Test reports processors - 8, CPUS - 32, with the following code:
no_of_processor=`tst_ncpus`
no_of_cpu=`tst_ncpus_conf`

tst_resm TINFO "processors - $no_of_processor, CPUS - $no_of_cpu"

I think the test itself got some issue, on those systems that didn't fail with this. They are actually failing with:
11:34:47 DEBUG| [stdout] startup='Sun Jun 9 11:24:08 2024'
11:34:47 DEBUG| [stdout] smt_smp_enabled 0 TINFO : Begin: SMT/SMP Enabled
11:34:47 DEBUG| [stdout] smt_smp_enabled 1 TPASS : SMP System
11:34:47 DEBUG| [stdout] smt_smp_enabled 0 TINFO : End: SMT/SMP Enabled
11:34:47 DEBUG| [stdout] tag=smt_smp_enabled stime=1717932248 dur=0 exit=exited stat=0 core=no cu=1 cs=3
11:34:47 DEBUG| [stdout] startup='Sun Jun 9 11:24:09 2024'
11:34:47 DEBUG| [stdout] smt_smp_affinity 0 TINFO : Begin: SMT/SMP Affinity
11:34:47 DEBUG| [stdout] smt_smp_affinity 0 TINFO : Get affinity through system call
11:34:47 DEBUG| [stdout] smt_smp_affinity 1 TFAIL : ht_affinity.c:226: System call getaffinity() is error.
11:34:47 DEBUG| [stdout]
11:34:47 DEBUG| [stdout] smt_smp_affinity 0 TINFO : Get affinity through system call
11:34:47 DEBUG| [stdout] smt_smp_affinity 1 TFAIL : ht_affinity.c:226: System call getaffinity() is error.
(repeat)