Ubuntu
linux package

timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

Bug #1887469 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Undecided
Unassigned
Xenial
Confirmed
Undecided
Unassigned
Bionic
Confirmed
Undecided
Unassigned
Eoan
Confirmed
Undecided
Unassigned
Focal
Confirmed
Undecided
Unassigned

Bug Description

Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches)
And B/E/F s390x as well.

<<<test_start>>>
tag=timer_settime01 stime=1594697076
cmdline="timer_settime01"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec
timer_settime01.c:70: INFO: Testing for general initialization:
timer_settime01.c:125: PASS: CLOCK_REALTIME was successful
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for setting old_value:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using periodic timer:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using absolute time:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)

HINT: You _MAY_ be missing kernel fixes, see:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f18ddc13af98

Summary:
passed 1
failed 46
skipped 8
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-186-generic 4.4.0-186.216
ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
Uname: Linux 4.4.0-186-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Mon Jul 13 22:59:54 2020
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c77779 crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-186-generic N/A
 linux-backports-modules-4.4.0-186-generic N/A
 linux-firmware 1.157.23
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
tags: added: kqa-blocker sru-20200629 ubuntu-ltp-syscalls
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Bionic):
status: New → Confirmed
Changed in linux (Ubuntu Eoan):
status: New → Confirmed
Changed in linux (Ubuntu Focal):
status: New → Confirmed
Changed in linux (Ubuntu Xenial):
status: New → Confirmed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue can be found on 4.4.0-185-generic as well.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

It looks like a test case issue after commit:
50a2cb874188c ("syscalls: Fix issues around calling syscalls with old timespec")
https://github.com/linux-test-project/ltp/commit/50a2cb874188c89e03501f9d68585d3e256f3fc7

Po-Hsu Lin (cypressyew)
tags: added: eoan
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Passed with Xenial 4.4 s390x in this cycle.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.