canonical-ubuntu-qa team mailing list archive

[Jürg Häfliger <1864642@xxxxxxxxxxxxxxxxxx>]

** Tags added: kernel-daily-bug

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1864642

Title:
  dscr_sysfs_test / futex_bench / tm-unavailable  in powerpc from
  ubuntu_kernel_selftests timeout on PowerPC nodes with B-5.3

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == SRU Justification ==
  Some specific tests in powerpc can take longer than the default 45
  seconds that added in commit 852c8cbf34d3 ("selftests/kselftest/runner.sh:
  Add 45 second timeout per test") to run, the following test result was
  collected across 2 Power8 nodes and 1 Power9 node in our pool:
    powerpc/benchmarks/futex_bench - 52s
    powerpc/dscr/dscr_sysfs_test - 116s
    powerpc/signal/signal_fuzzer - 88s
    powerpc/tm/tm_unavailable_test - 168s
    powerpc/tm/tm-poison - 240s

  Thus they will fail with TIMEOUT error.

  == Fix ==
  * 850507f3 ("selftests/powerpc: Turn off timeout setting for benchmarks, dscr, signal, tm")

  Only Eoan and newer kernel will need this fix.
  For Eoan, this patch can be applied with some context adjustment. 
  For Focal, there is a SAUCE patch which turned off timeout setting for 
  benchmarks and tm that needs to be reverted first, and this patch can
  be applied with some context adjustment too

  == Test ==
  Patch tested on PowerPC and it works as expected.

  == Regression Potential ==
  Low, changes limited to testing tools for PowerPC.

  
  == Original Bug Report ==
  Issue found on Power9 node baltar with B-5.3 (5.3.0-41.33~18.04.1-generic)

   # selftests: benchmarks: futex_bench
   # test: futex_bench
   # tags: git_version:unknown
   # time = 52.042224
   #
   not ok 5 selftests: benchmarks: futex_bench # TIMEOUT

   # selftests: dscr: dscr_sysfs_test
   # test: dscr_sysfs_test
   # tags: git_version:unknown
   #
   not ok 6 selftests: dscr: dscr_sysfs_test # TIMEOUT

  Need to check if this has something to do with the timeout setting
  like in bug 1864626

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: ppc64el
  Date: Tue Feb 25 11:23:58 2020
  ProcLoadAvg: 1.28 22.46 46.59 3/1347 62287
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3837 00:18:562 0 EOF
   2: POSIX  ADVISORY  WRITE 3864 00:18:588 0 EOF
   3: FLOCK  ADVISORY  WRITE 4515 00:18:463 0 EOF
   4: FLOCK  ADVISORY  WRITE 3844 00:18:579 0 EOF
   5: POSIX  ADVISORY  WRITE 1820 00:18:343 0 EOF
  ProcSwaps:
   Filename				Type		Size	Used	Priority
   /swap.img                               file		8388544	0	-2
  ProcVersion: Linux version 5.3.0-40-generic (buildd@bos02-ppc64el-007) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:15 UTC 2020
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 9
  cpu_freq:
   min:	2.862 GHz (cpu 79)
   max:	2.945 GHz (cpu 81)
   avg:	2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864642/+subscriptions