36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC

Bug #1850904 reported by Po-Hsu Lin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned
Disco
Invalid
Undecided
Unassigned

Bug Description

This issue was found on Disco, after re-enable the ubuntu-seccomp (bug 1850743) test for newer releases. So this is not a regression.

The test has passed with amd64, i386, but failed with s390x / PowerPC

36 test errored.
   batch name: 36-sim-ipc_syscalls
   test mode: c
   test type: bpf-sim
  Test 36-sim-ipc_syscalls%%001-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%002-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%003-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%004-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%005-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%006-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%007-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%008-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%009-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%010-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%011-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%012-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%013-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%014-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%015-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%016-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%017-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%018-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%019-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%020-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%021-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%022-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%023-00001 result: ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%024-00001 result: ERROR 36-sim-ipc_syscalls rc=14
   test mode: c
   test type: bpf-valgrind
  Test 36-sim-ipc_syscalls%%025-00001 result: SKIPPED (valgrind not installed)
   batch name: 37-sim-ipc_syscalls_be
   test mode: c
   test type: bpf-sim
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%001-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%002-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%003-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%004-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%005-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%006-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%007-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%008-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%009-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%010-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%011-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test arch: s390
  Test 37-sim-ipc_syscalls_be%%012-00001 result: ERROR 37-sim-ipc_syscalls_be rc=14
   test mode: c
   test type: bpf-valgrind

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-32-generic 5.0.0-32.34
ProcVersionSignature: User Name 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic s390x
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': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.2
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:

Date: Fri Nov 1 07:45:19 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB:

ProcKernelCmdLine: root=UUID=5e54b5c2-bab6-4007-b216-f26a243b0ca5
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-32-generic N/A
 linux-backports-modules-5.0.0-32-generic N/A
 linux-firmware 1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew)
tags: added: 5.0 ppc64el ubuntu-seccomp
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1850904

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Disco):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: ubuntu_seccomp failed with X/D s390x / PPC

This issue can be found on Xenial s390x / P8 as well.

summary: - ubuntu_seccomp failed with Disco
+ ubuntu_seccomp failed with X/D s390x / PPC
description: updated
Po-Hsu Lin (cypressyew)
summary: - ubuntu_seccomp failed with X/D s390x / PPC
+ ubuntu_seccomp failed with X/B/D s390x / PPC
tags: added: sru-20191111
Revision history for this message
Leo Le Bouter (lle-bout) wrote : Re: ubuntu_seccomp failed with X/B/D s390x / PPC

I am building software in CI on ppc64el and I am met with a variant of this issue.

https://gitlab.com/chromium-ppc64le/ungoogled-chromium/-/jobs/384098505

What I am building requires the system calls: __NR_shmat __NR_shmctl __NR_shmdt __NR_shmget
and it seems they are not present in <asm/unistd_64.h>, for some reason.

Here's the recipe: https://gitlab.com/chromium-ppc64le/ungoogled-chromium-ci-docker-image/blob/5db632353a7d8d57b583fc907aaf2985c1bc192a/Dockerfile

I tried on both bionic and disco, same issue.

Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: New → Triaged
tags: added: sru-20200106
Po-Hsu Lin (cypressyew)
tags: added: sru-20200127
Po-Hsu Lin (cypressyew)
summary: - ubuntu_seccomp failed with X/B/D s390x / PPC
+ 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed
+ with X/B/D s390x / PPC
tags: added: sru-20200217
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Didn't see this on X/B PPC.
* 4.4.0-180.210
* 4.15.0-102.103

Looks like this has been fixed, closing this bug.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu Disco):
status: Incomplete → Invalid
Changed in ubuntu-kernel-tests:
status: Triaged → Fix Released
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

For comment #5, nor seeing this on s390x.

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

Other bug subscribers

Remote bug watches

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