Seen this issue on metal:fozzie as well. Not a regression. Fails because
Hyperthreading is not enabled (noble:linux-lowlatency 6.8.0-40.40.1 SRU
Cycle: 2024.07.08).
10:31:59 INFO | START ubuntu_ltp_stable.hyperthreading
ubuntu_ltp_stable.hyperthreading timeout=12600 timestamp=1723199519
localtime=Aug 09 10:31:59
10:31:59 DEBUG| Persistent state client._record_indent now set to 2
10:31:59 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_stable.hyperthreading', 'ubuntu_ltp_stable.hyperthreading')
10:31:59 DEBUG| Waiting for pid 86706 for 12600 seconds
10:31:59 WARNI| System python is too old, crash handling disabled
10:31:59 INFO | == Test Suite Summary ==
10:31:59 INFO | 2 test cases failed
10:31:59 INFO | Failed test cases : smt_smp_affinity smt_smp_enabled
10:31:59 DEBUG| [stdout] startup='Fri Aug 9 10:31:59 2024'
10:31:59 DEBUG| [stdout] smt_smp_enabled 0 TINFO : Begin: SMT/SMP Enabled
10:31:59 DEBUG| [stdout] smt_smp_enabled 1 TCONF : ltpapicmd.c:188:
Enable:/sys/devices/system/cpu/cpuX/online
10:31:59 DEBUG| [stdout] smt_smp_enabled 0 TINFO : End: SMT/SMP Enabled
10:31:59 DEBUG| [stdout] tag=smt_smp_enabled stime=1723199519 dur=0 exit=exited
stat=1 core=no cu=0 cs=1
10:31:59 DEBUG| [stdout] startup='Fri Aug 9 10:31:59 2024'
10:31:59 DEBUG| [stdout] smt_smp_affinity 0 TINFO : Begin: SMT/SMP
Affinity
10:31:59 DEBUG| [stdout] smt_smp_affinity 1 TCONF : ltpapicmd.c:188:
cpuX:offline
10:31:59 DEBUG| [stdout] smt_smp_affinity 0 TINFO : End: SMT/SMP Affinity
10:31:59 DEBUG| [stdout] tag=smt_smp_affinity stime=1723199519 dur=0
exit=exited stat=1 core=no cu=0 cs=1
--
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
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
