361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node

[Po-Hsu Lin]

This test will take about 2 hours to run on node wright (ThunderX ARM64) with Xenial kernel.
Test history:
4.4.0-155.182 - 1h45m
4.4.0-152.179 - 1h57m
4.4.0-150.176 - 2h00m
4.4.0-149.175 - 2h03m
4.4.0-147.173 - 1h55m
4.4.0-146.172 - 1h57m
4.4.0-145.171 - 1h59m

However it took about 25min to run on a Moonshot ARM64 (ms10-35-mcdivittB0-kernel) with Xenial kernel.
Test history:
4.4.0-155.182 - 23m
4.4.0-152.179 - 24m
4.4.0-150.176 - 23m
4.4.0-149.175 - 23m
4.4.0-147.173 - 23m
4.4.0-146.172 - 23m
4.4.0-145.171 - 24m

Not sure why there is such a huge difference, but it might needs to be investigated.

This is node wright performance with this test against different kernels:
5.0.0-21.22 - 1h20m
4.18.0-26.27 - 1h18m
5.0.0-21.22~18.04.1 - 1h17m
4.15.0-55.60 - 1h23m
4.15.0-55.60~16.04.2 - 1h23m

And node ms10-35-mcdivittB0-kernel against different kernels:
5.0.0-21.22 - 17m
4.18.0-26.27 - 17m
5.0.0-21.22~18.04.1 - 17m
4.15.0-55.60 - 17m
4.15.0-55.60~16.04.2 - 17m

Step to run the test:
  sudo apt-get install git python-minimal python-yaml gdb -y
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  rm -fr autotest/client/tests
  ln -sf ~/autotest-client-tests autotest/client/tests
  mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
  mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
  mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/
  AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-154-generic 4.4.0-154.181
ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic aarch64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jul 10 08:25 seq
 crw-rw---- 1 root audio 116, 33 Jul 10 08:25 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CurrentDmesg:

Date: Thu Jul 11 02:56:23 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:

ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-154-generic N/A
 linux-backports-modules-4.4.0-154-generic N/A
 linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
dmi.product.name: ThunderX CRB
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Cavium

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1836134

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.