memcg_use_hierarchy from controllers test suite in LTP failed

Bug #1829989 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
Cosmic
Won't Fix
Undecided
Unassigned
linux-aws (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Invalid
Undecided
Unassigned
Cosmic
Won't Fix
Undecided
Unassigned

Bug Description

startup='Wed May 22 05:59:07 2019'
memcg_use_hierarchy_test 1 TINFO: Starting test 1
sh: echo: I/O error
memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
memcg_use_hierarchy_test 2 TINFO: Starting test 2
sh: echo: I/O error
memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed unexpectedly
memcg_use_hierarchy_test 3 TINFO: Starting test 3
sh: echo: I/O error
memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy failed as expected
tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no cu=5 cs=5

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:
 [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database
 [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Date: Wed May 22 07:33:33 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 1829989

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
Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu Bionic):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Cosmic):
status: New → Confirmed
Changed in ubuntu-kernel-tests:
status: New → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-ltp
Po-Hsu Lin (cypressyew)
tags: added: cosmic linux-kvm sru-20190603
Sean Feole (sfeole)
tags: added: sru-20191202
Sean Feole (sfeole)
tags: added: arm64
Sean Feole (sfeole)
Changed in linux-aws (Ubuntu):
status: New → Triaged
Sean Feole (sfeole)
tags: added: sru-20200217
Sean Feole (sfeole)
tags: added: sru-20200427
tags: added: sru-20200921
tags: added: 5.4 aws focal
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Spotted on Focal/linux-azure 5.4.0-1029.29

tags: added: azure
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 5.8.0-31.33

tags: added: 5.8 groovy sru-20201109
tags: added: sru-20210104
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Found on bionic/ibm-gt 4.15.0-1084.93

tags: added: ibm-gt
tags: added: sru-20210125
tags: added: fips
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Didn't see this on B-oracle-5.4, B-oracle-4.15 this cycle (4.15.0-1066, 5.4.0-1039.42~18.04.1)

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

Failed on Focal OEM-5.10 with:
 memcg_use_hierarchy_test 1 TFAIL: process is not killed
 rmdir: failed to remove 'subgroup': No such file or directory

5.10.0-1017.18-oem

tags: added: 5.10 sru-20210222
tags: removed: ibm-gt
tags: added: 5.11 hirsute sru-20210510
tags: added: realtime sru-20210531
Revision history for this message
Krzysztof Kozlowski (krzk) wrote (last edit ):

Found on focal v5.11 kernels (but not v5.8): 5.11.0-1009-aws (AWS c4.8xlarge) and 5.11.0-22-generic (Azure Standard_F32s_v2). It seems it fails only on bigger instances (32 CPUs or more).

On Focal v5.11 it might be slightly different issue:
#####
memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_use_hierarchy_test 1 TINFO: test if one of the ancestors goes over its limit, the proces will be killed
mkdir: cannot create directory ‘subgroup’: Cannot allocate memory
/home/ubuntu/ltp-install/testcases/bin/memcg_use_hierarchy_test.sh: 22: cd: can't cd to subgroup
memcg_use_hierarchy_test 1 TINFO: Running memcg_process --mmap-lock1 -s 8192
memcg_use_hierarchy_test 1 TFAIL: process is not killed
rmdir: failed to remove 'subgroup': No such file or directory
#####

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 Cosmic):
status: New → Confirmed
Changed in ubuntu-kernel-tests:
assignee: nobody → Krzysztof Kozlowski (krzk)
Changed in ubuntu-kernel-tests:
status: Confirmed → In Progress
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :
Changed in linux-aws (Ubuntu):
status: Triaged → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu Bionic):
status: Confirmed → Invalid
Changed in linux-aws (Ubuntu Bionic):
status: Confirmed → Invalid
Changed in linux (Ubuntu Cosmic):
status: Confirmed → Invalid
status: Invalid → Won't Fix
Changed in linux-aws (Ubuntu Cosmic):
status: Confirmed → Won't Fix
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Seeing on hirsute/linux with different output. questioning if related. :

376. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: timeout per run is 0h 5m 0s
377. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
378. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: Test memory.usage_in_bytes
379. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304
380. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 306142
381. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 306142
382. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4325376, 4194304 expected
383. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 2 TINFO: Test memory.memsw.usage_in_bytes
384. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304
385. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 2 TINFO: Warming up pid: 306158
386. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 306158
387. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 2 TFAIL: memory.memsw.usage_in_bytes is 4325376, 4194304 expected
388. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 3 TINFO: AppArmor enabled, this may affect test results
389. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 3 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
390. 06/23 04:43:01 DEBUG| utils:0153| [stdout] memcg_usage_in_bytes_test 3 TINFO: loaded AppArmor profiles: none
391. 06/23 04:43:01 DEBUG| utils:0153| [stdout]

tags: added: sru-20210719
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

Fix for memcg_use_hierarchy_test and memcg_subgroup_charge.sh released upstream:
https://github.com/linux-test-project/ltp/commit/403b92d3b2d40ff1f54dc056d4d573ff2f32f0da
(also similar cause in memcg_stat_test https://github.com/linux-test-project/ltp/commit/4ecfd3308fc7e85b80d8740540ed7c909484037b )

Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
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.