leapsec01 from ubuntu_ltp_syscalls failed on KVM nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Thadeu Lima de Souza Cascardo | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Issue found on KVM node with Bionic kernel, passed with two other bare-metals.
This issue can be found on B-KVM / D-KVM kernel on KVM nodes as well (not X-KVM)
Steps to reproduce:
git clone --depth=1 https:/
cd ltp; make autotools; ./configure; make; sudo make install
echo "leapsec01 leapsec01" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs
<<<test_start>>>
tag=leapsec01 stime=1565089809
cmdline="leapsec01"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
incrementing stop
leapsec01.c:130: INFO: test start at 11:10:09.780688056
leapsec01.c:100: INFO: now is 11:10:09.780752712
leapsec01.c:104: INFO: sleep until 11:10:10.780752712
leapsec01.c:112: INFO: now is 11:10:10.780962327
leapsec01.c:115: INFO: hrtimer early expiration is not detected.
leapsec01.c:138: INFO: scheduling leap second 00:00:00.000000000
leapsec01.c:144: INFO: setting time to 23:59:58.000000000
leapsec01.c:88: INFO: 23:59:58.424557000 adjtimex: clock synchronized
leapsec01.c:88: INFO: 23:59:58.000454000 adjtimex: clock synchronized
leapsec01.c:88: INFO: 23:59:58.000467000 adjtimex: clock synchronized
leapsec01.c:88: INFO: 23:59:58.000479000 adjtimex: clock synchronized
leapsec01.c:88: INFO: 11:10:11.
leapsec01.c:88: INFO: 11:10:11.
leapsec01.c:88: INFO: 11:10:12.
leapsec01.c:88: INFO: 11:10:12.
leapsec01.c:88: INFO: 11:10:13.
leapsec01.c:88: INFO: 11:10:13.
leapsec01.c:88: INFO: 11:10:14.
leapsec01.c:88: INFO: 11:10:14.
leapsec01.c:88: INFO: 11:10:15.
leapsec01.c:88: INFO: 11:10:15.
leapsec01.c:88: INFO: 11:10:16.
leapsec01.c:88: INFO: 11:10:16.
leapsec01.c:88: INFO: 11:10:17.
leapsec01.c:88: INFO: 11:10:17.
leapsec01.c:88: INFO: 11:10:18.
leapsec01.c:88: INFO: 11:10:18.
leapsec01.c:88: INFO: 11:10:19.
leapsec01.c:88: INFO: 11:10:19.
leapsec01.c:88: INFO: 11:10:20.
leapsec01.c:88: INFO: 11:10:20.
leapsec01.c:88: INFO: 11:10:21.
leapsec01.c:88: INFO: 11:10:21.
leapsec01.c:88: INFO: 11:10:22.
leapsec01.c:88: INFO: 11:10:22.
leapsec01.c:88: INFO: 11:10:23.
leapsec01.c:88: INFO: 11:10:23.
leapsec01.c:88: INFO: 11:10:24.
leapsec01.c:88: INFO: 11:10:24.
leapsec01.c:88: INFO: 11:10:25.
leapsec01.c:88: INFO: 11:10:25.
leapsec01.c:88: INFO: 11:10:26.
leapsec01.c:88: INFO: 11:10:26.
leapsec01.c:88: INFO: 11:10:27.
leapsec01.c:88: INFO: 11:10:27.
leapsec01.c:88: INFO: 11:10:28.
leapsec01.c:88: INFO: 11:10:28.
leapsec01.c:88: INFO: 11:10:29.
leapsec01.c:88: INFO: 11:10:29.
leapsec01.c:88: INFO: 11:10:30.
leapsec01.c:88: INFO: 11:10:30.
leapsec01.c:88: INFO: 11:10:31.
leapsec01.c:88: INFO: 11:10:31.
leapsec01.c:88: INFO: 11:10:32.
leapsec01.c:88: INFO: 11:10:32.
leapsec01.c:88: INFO: 11:10:33.
leapsec01.c:88: INFO: 11:10:33.
leapsec01.c:88: INFO: 11:10:34.
leapsec01.c:88: INFO: 11:10:34.
leapsec01.c:88: INFO: 11:10:35.
leapsec01.c:88: INFO: 11:10:35.
leapsec01.c:88: INFO: 11:10:36.
leapsec01.c:88: INFO: 11:10:36.
leapsec01.c:88: INFO: 11:10:37.
leapsec01.c:88: INFO: 11:10:37.
leapsec01.c:88: INFO: 11:10:38.
leapsec01.c:88: INFO: 11:10:38.
leapsec01.c:88: INFO: 11:10:39.
leapsec01.c:88: INFO: 11:10:39.
leapsec01.c:88: INFO: 11:10:40.
leapsec01.c:88: INFO: 11:10:40.
leapsec01.c:88: INFO: 11:10:41.
leapsec01.c:88: INFO: 11:10:41.
leapsec01.c:88: INFO: 11:10:42.
leapsec01.c:88: INFO: 11:10:42.
leapsec01.c:84: BROK: adjtimex status 8208 not set
Summary:
passed 0
failed 0
skipped 0
warnings 0
<<<execution_
initiation_
duration=34 termination_
cutime=0 cstime=0
<<<test_end>>>
tags: | added: 4.15 5.0 amd64 sru-20190722 ubuntu-ltp-syscalls |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1839135
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.