memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic

Bug #1836694 reported by Po-Hsu Lin on 2019-07-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned

Bug Description

This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.)

<<<test_start>>>
tag=memcg_test_3 stime=1563249678
cmdline="memcg_test_3"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
Test timeouted, sending SIGKILL!
tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
tst_test.c:1141: BROK: Test killed! (timeout?)

Summary:
passed 0
failed 0
skipped 0
warnings 0
tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM
<<<execution_status>>>

When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail:
  * cgroup_fj_function_memory
  * cgroup_fj_stress_memory_10_3_each
  * cgroup_fj_stress_memory_10_3_none
  * cgroup_fj_stress_memory_10_3_one
  * cgroup_fj_stress_memory_1_200_each
  * cgroup_fj_stress_memory_1_200_none
  * cgroup_fj_stress_memory_1_200_one
  * cgroup_fj_stress_memory_200_1_each
  * cgroup_fj_stress_memory_200_1_none
  * cgroup_fj_stress_memory_200_1_one
  * cgroup_fj_stress_memory_2_2_each
  * cgroup_fj_stress_memory_2_2_none
  * cgroup_fj_stress_memory_2_2_one
  * cgroup_fj_stress_memory_2_9_each
  * cgroup_fj_stress_memory_2_9_none
  * cgroup_fj_stress_memory_2_9_one
  * cgroup_fj_stress_memory_3_3_each
  * cgroup_fj_stress_memory_3_3_none
  * cgroup_fj_stress_memory_3_3_one
  * cgroup_fj_stress_memory_4_4_each
  * cgroup_fj_stress_memory_4_4_none
  * cgroup_fj_stress_memory_4_4_one

Steps to run this:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "memcg_test_3 memcg_test_3" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-54-generic 4.15.0-54.58
ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic aarch64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jul 16 03:46 seq
 crw-rw---- 1 root audio 116, 33 Jul 16 03:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: arm64
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:
Date: Tue Jul 16 04:16:14 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB:

ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-54-generic N/A
 linux-backports-modules-4.15.0-54-generic N/A
 linux-firmware 1.173.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Po-Hsu Lin (cypressyew) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Po-Hsu Lin (cypressyew) on 2019-07-16
tags: added: 4.15 sru-20190701 ubuntu-ltp
Po-Hsu Lin (cypressyew) wrote :

This issue could be found on B-gcp as well.

But set the LTP_TIMEOUT_MUL to 3 can make it pass.

It tooks:
real 8m50.670s
user 1m54.287s
sys 4m39.889s

On GCP, so LTP_TIMEOUT_MUL=3 is quite enough.

Next is to see if this fix works for Moonshot ARM64.

Po-Hsu Lin (cypressyew) wrote :

On Moonshot ARM64,
the test result is a bit unstable, sometimes it will pass within 2min, sometimes it will take 8, some even timeout with 30min threshold.

I think it's better to just fix it for virtual env now.

Po-Hsu Lin (cypressyew) wrote :

Also, this has timeout on AWS a1.medium (arm64) with B-4.15 AWS kernel.
It looks like this is not a VM

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

Other bug subscribers