canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #04364
[Bug 2017650] Re: hyperthreading in ubuntu_ltp_stable failed on J-ibm with node onibi
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)
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2017650
Title:
hyperthreading in ubuntu_ltp_stable failed on J-ibm with node onibi
Status in ubuntu-kernel-tests:
New
Bug description:
This failure was hinted without a proper bug report. It seems this is
specific to node onibi.
Test log:
Failed test cases : smt_smp_affinity smt_smp_enabled
startup='Tue Feb 21 01:51:52 2023'
smt_smp_enabled 0 TINFO : Begin: SMT/SMP Enabled
smt_smp_enabled 1 TCONF : ltpapicmd.c:188: Enable:/sys/devices/system/cpu/cpuX/online
smt_smp_enabled 0 TINFO : End: SMT/SMP Enabled
tag=smt_smp_enabled stime=1676944312 dur=0 exit=exited stat=1 core=no cu=0 cs=0
startup='Tue Feb 21 01:51:52 2023'
smt_smp_affinity 0 TINFO : Begin: SMT/SMP Affinity
smt_smp_affinity 1 TCONF : ltpapicmd.c:188: cpuX:offline
smt_smp_affinity 0 TINFO : End: SMT/SMP Affinity
tag=smt_smp_affinity stime=1676944312 dur=0 exit=exited stat=1 core=no cu=0 cs=0
Nothing interesting in dmesg:
[104477.578371] LTP: starting smt_smp_enabled (smt_smp_enabled.sh)
[104477.588795] LTP: starting smt_smp_affinity (smt_smp_affinity.sh)
With "set -x" added to test test script (smt_smp_enabled.sh,
smt_smp_affinity.sh) it can help us to identify the failing point:
smt_smp_enabled test (smt_smp_enabled.sh):
<<<test_start>>>
tag=smt_smp_enabled stime=1682415438
cmdline="smt_smp_enabled.sh"
contacts=""
analysis=exit
<<<test_output>>>
+ tst_resm TINFO Begin: SMT/SMP Enabled
smt_smp_enabled 0 TINFO : Begin: SMT/SMP Enabled
+ [ -f ./ht_enabled ]
+ ./ht_enabled
+ ret_value=0
+ [ 0 -ne 0 ]
+ tst_ncpus
+ no_of_processor=4
+ tst_ncpus_conf
+ no_of_cpu=32
+ [ 4 -lt 32 ]
+ test_op=Enable:/sys/devices/system/cpu/cpuX/online
+ tst_resm TCONF Enable:/sys/devices/system/cpu/cpuX/online
smt_smp_enabled 1 TCONF : ltpapicmd.c:188: Enable:/sys/devices/system/cpu/cpuX/online
+ tst_resm TINFO End: SMT/SMP Enabled
smt_smp_enabled 0 TINFO : End: SMT/SMP Enabled
+ TFAILCNT=1
+ exit 1
smt_smp_affinity test (smt_smp_affinity.sh):
<<<test_output>>>
incrementing stop
smt_smp_affinity 0 TINFO : Begin: SMT/SMP Affinity
+ [ -f ./ht_enabled ]
+ ./ht_enabled
+ ret_value=0
+ [ 0 -ne 0 ]
+ tst_ncpus
+ no_of_processor=4
+ tst_ncpus_conf
+ no_of_cpu=32
+ [ 4 -lt 32 ]
+ tst_resm TCONF cpuX:offline
smt_smp_affinity 1 TCONF : ltpapicmd.c:188: cpuX:offline
+ tst_resm TINFO End: SMT/SMP Affinity
smt_smp_affinity 0 TINFO : End: SMT/SMP Affinity
+ TFAILCNT=1
+ exit 1
The failure is because no_of_processor < no_of_cpu.
This issue still exists with the latest LTP upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2017650/+subscriptions