cpuacct_100_100 from controllers test suite in LTP failed

Bug #1829978 reported by Po-Hsu Lin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Krzysztof Kozlowski
linux (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Invalid
Undecided
Unassigned
linux-aws (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Invalid
Undecided
Unassigned

Bug Description

 startup='Wed May 22 06:50:45 2019'
 cpuacct 1 TINFO: timeout per run is 0h 5m 0s
 cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
 cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
 /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork
 tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 22 02:57 seq
 crw-rw---- 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Wed May 22 06:59:27 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=576666e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-50-generic N/A
 linux-backports-modules-4.15.0-50-generic N/A
 linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
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 1829978

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 Bionic):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Test passed with Cosmic:
 tag=cpuacct_100_100 stime=1558480324
 cmdline="cpuacct.sh 100 100"
 contacts=""
 analysis=exit
 <<>>
 cpuacct 1 TINFO: timeout per run is 0h 5m 0s
 cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
 cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
 cpuacct 1 TPASS: cpuacct.usage is not equal to 0 for every subgroup
 cpuacct 1 TPASS: cpuacct.usage equal to subgroup*/cpuacct.usage
 cpuacct 2 TINFO: removing created directories

 Summary:
 passed 2
 failed 0
 skipped 0
 warnings 0

Changed in linux (Ubuntu Cosmic):
status: New → Fix Released
Po-Hsu Lin (cypressyew)
tags: added: linux-kvm sru-20190603 ubuntu-ltp
Sean Feole (sfeole)
tags: added: azure sru-20190902
Sean Feole (sfeole)
tags: added: aws linux-aws-edge
Sean Feole (sfeole)
no longer affects: linux (Ubuntu Cosmic)
no longer affects: linux-aws (Ubuntu Cosmic)
tags: added: sru-20190930
tags: added: disco
Sean Feole (sfeole)
tags: added: sru-20200217
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: New → Confirmed
tags: added: sru-20200406
Steve Langasek (vorlon)
Changed in linux (Ubuntu Disco):
status: New → Won't Fix
Changed in linux-aws (Ubuntu Disco):
status: New → Won't Fix
Sean Feole (sfeole)
tags: added: arm64 sru-20200629
no longer affects: linux (Ubuntu Disco)
no longer affects: linux-aws (Ubuntu Disco)
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Spotted on Focal/azure : 5.4.0-1029.29 : amd64

tags: added: focal sru-20200921
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

failed on Bionic/azure-4.15 : 4.15.0-1097.107 : amd64

tags: added: 4.15
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Found on Groovy/linux 5.8.0-31.33

tags: added: 5.8 groovy sru-20201109
tags: added: sru-20210104
Revision history for this message
Francis Ginther (fginther) wrote :

Seen with linux-oracle 4.15.0-1065.73.

tags: added: oracle sru-20210125
tags: added: 5.4 sru-20210315
tags: added: sru-20210412
tags: added: fips
Revision history for this message
Ian May (ian-may) wrote :

bionic/linux-aws: 4.15.0-1103.110

tags: added: sru-20210510
Revision history for this message
Ian May (ian-may) wrote :

Found on bionic/linux-aws-fips: 4.15.0-2045.47

Revision history for this message
Ian May (ian-may) wrote :

Found on bionic/linux-aws-5.4: 5.4.0-1049.51~18.04.1

Revision history for this message
Ian May (ian-may) wrote :

Found on bionic/linux-azure-4.15: 4.15.0-1115.128

Revision history for this message
Krzysztof Kozlowski (krzk) wrote (last edit ):

Found on Azure Standard_B1ms instances:
 - hirsute/linux-azure 5.11.0-1007.7
 - groovy/linux-azure 5.8.0-1033.35
 - groovy/linux-azure 5.8.0-1034.36-azure
 - focal/linux-azure 5.8.0-1033.35~20.04.1
 - focal/linux-azure 5.4.0-1049.51
 - bionic/linux-azure 5.4.0-1049.51~18.04.1

Does not appear on other instances, therefore I propose to skip this part on Standard_B1ms.

On Standard_B1ms this seems to be systemd runtime configuration limit. Visible in dmesg:
[ 926.863344] LTP: starting cpuacct_100_100 (cpuacct.sh 100 100)
[ 934.298505] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-3.scope

Changed in ubuntu-kernel-tests:
assignee: nobody → Krzysztof Kozlowski (krzk)
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

AWS t2.small (1 CPU, 2 GB RAM) fails the same on focal/linux-aws 5.4.0-1045-aws:

cpuacct 1 TINFO: timeout per run is 0h 5m 0s
cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
/home/ubuntu/ltp-install/testcases/bin/cpuacct.sh: 0: Cannot fork

Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

AWS t3.xlarge (4 CPU, 16 GB RAM) is fine. If booted with maxcpus=1 - still works. If booted with mem=2048M, it fails the same as t2.small.

Changed in ubuntu-kernel-tests:
status: Confirmed → In Progress
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :
tags: added: sru-20210531
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-aws (Ubuntu Bionic):
status: New → Confirmed
Changed in linux-aws (Ubuntu):
status: New → Confirmed
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

Found on hirsute/azure 5.11.0-1007.7

tags: added: 5.11
Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu Bionic):
status: Incomplete → Invalid
Changed in linux-aws (Ubuntu):
status: Confirmed → Invalid
Changed in linux-aws (Ubuntu Bionic):
status: Confirmed → Invalid
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.