This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864172

Title:
  ftrace test in ubuntu_kernel_selftests will timeout randomly

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  A new timeout feature was added to kselftests in commit 852c8cbf
  (selftests/kselftest/runner.sh: Add 45 second timeout per test)

  However the ftrace test will take much longer than 45 seconds to run,
  thus you will see it failed with:
     not ok 1 selftests: ftrace: ftracetest # TIMEOUT

  == Fix ==
  * 9fab89cc (tracing/selftests: Turn off timeout setting)

  This patch will turn off the timeout setting for the ftrace test.
  It can be cherry-picked into B/D/E/F, we don't run this test in X so it
  can be skipped.

  Note that we don't have 852c8cbf in B/D, but I think it's still OK to
  fix them as the change is really small, and if they got that patch in
  the future we don't need to look back on this.

  == Test ==
  Patch tested directly on KVM nodes. It works as expected.

  == Regression Potential ==
  Low, trivial change limited to testing tools.

  == Original Bug Report ==
  Issue found on Eoan

  this test will timeout quite randomly before the test can complete:

  1st attempt:
   # [23] ftrace - function trace on module   [PASS]
   # [24] ftrace - function profiling#
   not ok 1 selftests: ftrace: ftracetest # TIMEOUT

  2nd attemp:
  # [31] Kprobe dynamic event - adding and removing     [PASS]
  # [32] Kprobe dynamic event - busy event check#
  not ok 1 selftests: ftrace: ftracetest # TIMEOUT

  3rd attempt:
  # [35] Kprobe event string type argument      [PASS]
  # [36] Kprobe event symbol argument#
  not ok 1 selftests: ftrace: ftracetest # TIMEOUT

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: User Name 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Feb 21 09:05 seq
   crw-rw---- 1 root audio 116, 33 Feb 21 09:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu8.2
  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:
  Date: Fri Feb 21 09:09:06 2020
  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:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=29438a95-0e7a-484b-a1fb-527f0e3d2e06 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware                            1.183.4
  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: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to