This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801856
Title:
seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty
Status in Stress-ng:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Didn't see this on amd64 / i386, but it can be reproduced on power8
and ARM64
seccomp STARTING
seccomp RETURNED 2
seccomp FAILED
stress-ng: debug: [7528] 8 processors online, 8 processors configured
stress-ng: info: [7528] dispatching hogs: 4 seccomp
stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist
stress-ng: info: [7528] cache allocate: using built-in defaults as unable
to determine cache details
stress-ng: debug: [7528] cache allocate: default cache size: 2048K
stress-ng: debug: [7528] starting stressors
stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0)
stress-ng: debug: [7528] 4 stressors spawned
stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1)
stress-ng: fail: [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed,
errno=22 (Invalid argument)
stress-ng: fail: [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed,
errno=22 (Invalid argument)
stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2)
stress-ng: fail: [7530] stress-ng-seccomp: aborting because of unexpected
failure in child process
stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1)
stress-ng: fail: [7529] stress-ng-seccomp: aborting because of unexpected
failure in child process
stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0)
stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3)
stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7529] terminated
stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7530] terminated
stress-ng: fail: [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed,
errno=22 (Invalid argument)
stress-ng: fail: [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed,
errno=22 (Invalid argument)
stress-ng: fail: [7532] stress-ng-seccomp: aborting because of unexpected
failure in child process
stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2)
stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7531] terminated
stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7532] terminated
stress-ng: info: [7528] unsuccessful run completed in 0.00s
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-161-generic 3.13.0-161.211
ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
Uname: Linux 3.13.0-161-generic aarch64
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.14.1-0ubuntu3.29
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg:
Date: Tue Nov 6 06:23:27 2018
IwConfig:
lo no wireless extensions.
enp1s0 no wireless extensions.
enp1s0d1 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
PciMultimedia:
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
linux-restricted-modules-3.13.0-161-generic N/A
linux-backports-modules-3.13.0-161-generic N/A
linux-firmware 1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1801856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
